select_page
Select a page as a context for future tool calls.
This record as markdown: /tools/async23-chrome-devtools-mcp/select-page.md
What select_page does on Chrome Devtools
AI agents invoke select_page to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why select_page is rated High
This tool sets the active page context that affects all subsequent tool calls in a Chrome DevTools session. While it may appear to be a simple state selection, it influences execution context for future operations (including potentially destructive or financial ones). It interacts with browser page state and its effects depend on which page is selected, placing it in the Execute category rather than a pure Read.
From the tool's definition Select a page as a context for future tool calls
Attacks that exploit this kind of access
The rule that runs select_page 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 select_page, this is the rule to start with:
select_page stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 select_page call is checked against it from then on.
Questions about select_page
Select a page as a context for future tool calls. It is categorised as a Execute tool in the Chrome Devtools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for select_page: 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.
select_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the select_page 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 select_page. 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.
select_page 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.
Across the catalogue