This record as markdown: /tools/async23-chrome-devtools-mcp/get-tab-id.md
What get_tab_id does on Chrome Devtools
AI agents call get_tab_id to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_tab_id is rated Low
This tool retrieves metadata (a tab identifier) from the Chrome DevTools API. It performs no writes, deletions, code execution, or financial operations. The tab ID is a read-only identifier needed to reference browser tabs in subsequent operations. Even in a misuse scenario, obtaining a tab ID alone presents minimal risk—it is merely a reference value with no autonomous impact on browser state or user data.
From the tool's definition Tool name 'get_tab_id' and description 'Get the tab ID of the page' indicate a retrieval operation that queries state without modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_tab_id safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tab_id, this is the rule to start with:
get_tab_id is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every get_tab_id call is checked against it from then on.
Questions about get_tab_id
Get the tab ID of the page. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_tab_id: 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 Devtools. Nothing to install.
get_tab_id 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_tab_id 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_tab_id. 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_tab_id is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Devtools, and thousands of servers like it.
This server
Across the catalogue