select_page
Select a page as a context for future tool calls.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/select-page.md
What select_page does on Chrome DevTools MCP
AI agents use select_page to create or update resources in Chrome DevTools MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome DevTools MCP environment.
Why select_page is rated Medium
An AI agent can call select_page faster than any human can review: one bad instruction and it creates or modifies resources in Chrome DevTools MCP by the hundred, each call as confident as the last.
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 MCP, 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 capped: an agent stuck in a loop can't make hundreds of changes 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 MCP, 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 Write tool in the Chrome DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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 MCP. Nothing to install.
select_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 (anirbandz/chrome_mcp_devtool). 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