AI-powered semantic search across browser tabs
AI agents call search_tabs_content to retrieve information from Chrome MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches existing tab content without creating, modifying, deleting, or executing any operations. While the Chrome MCP server overall enables browser automation (Execute/Destructive potential), this specific tool is limited to information retrieval. Severity is low because search operations have no side effects and minimal blast radius if misused by an AI agent.
From the tool's definition Tool description explicitly states 'semantic search across browser tabs' with no modification, deletion, or execution capabilities mentioned. The name 'search_tabs_content' and description indicate purely retrieval/query functionality.
Attacks that exploit this kind of access
AI-powered semantic search across browser tabs. It is categorised as a Read tool in the Chrome MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for search_tabs_content: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Chrome MCP Server. Nothing to install.
search_tabs_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_tabs_content rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for search_tabs_content. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
search_tabs_content is provided by the Chrome MCP Server MCP server (standbyme626/mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →