search

Legitimate use cases are limited. It could be used by an extension that integrates search functionality in a novel way.

Example:

• An extension with its own search box in a popup or side panel that, when used, forwards the query to the user's configured default search engine.

{
  "name": "My Search Helper",
  "version": "1.0",
  "manifest_version": 3,
  "permissions": [
    "search"
  ]
}

Why is it not risky?

This permission by itself is safe. It only allows an extension to perform a search using whatever search engine you have already set as your default (like Google or DuckDuckGo).

The real danger comes from extensions that try to change your default search engine, which often points you to a spammy or ad-filled site. That capability is now heavily restricted by Google. This specific search permission doesn't allow that; it just uses your existing setting.

This example performs a search for "chrome extensions" in a new tab using the default search engine.

// background.js or popup.js

function performSearch() {
  chrome.search.query({
    text: "chrome extensions",
    // disposition can be "CURRENT_TAB", "NEW_TAB", or "NEW_WINDOW"
    disposition: "NEW_TAB"
  }, () => {
    if (chrome.runtime.lastError) {
      console.error(chrome.runtime.lastError.message);
    } else {
      console.log("Search opened in a new tab.");
    }
  });
}

// Call this from a user action.
// performSearch();