List all open browser tabs with their id, title, url, and active status.
AI agents call list_tabs to retrieve information from Chrome Extension MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves information about open tabs (id, title, url, active status) with no side effects. It is a read-only query operation. The severity is low because exposing tab metadata carries minimal risk—an agent could learn what sites are open, but cannot interact with them or cause damage through this tool alone.
From the tool's definition Tool name 'list_tabs' and description 'List all open browser tabs with their id, title, url, and active status' indicate a query operation that retrieves tab metadata without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all open browser tabs with their id, title, url, and active status. It is categorised as a Read tool in the Chrome Extension MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Chrome Extension MCP Bridge MCP server in PolicyLayer and add a rule for list_tabs: 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 Extension MCP Bridge. Nothing to install.
list_tabs 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 list_tabs 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 list_tabs. 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.
list_tabs is provided by the Chrome Extension MCP Bridge MCP server (ivoglent/chrome-mcp-bridge). 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 →