List all browser windows and tabs
AI agents call get_windows_and_tabs 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 metadata about the browser's current window and tab structure. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could learn which tabs and windows are open, potentially exposing information about user activity, but cannot act upon that information alone. This is a clear Read operation.
From the tool's definition Tool name 'get_windows_and_tabs' and description 'List all browser windows and tabs' indicate a query operation that retrieves information about open browser state without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all browser windows and 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 get_windows_and_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 MCP Server. Nothing to install.
get_windows_and_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 get_windows_and_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 get_windows_and_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.
get_windows_and_tabs is provided by the Chrome MCP Server MCP server (mnisred/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 →