Get a list of pages${args?.categoryExtensions ?
AI agents call list_pages to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists data (pages currently open in the Chrome browser) with no side effects. It is a pure read operation used for inspection and does not execute code, modify data, or affect browser state beyond observation. Even in the context of browser automation via DevTools, this is a safe reconnaissance operation with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'list_pages' and description 'Get a list of pages' indicate a query operation that retrieves information about open browser pages without modifying state.
Attacks that exploit this kind of access
Get a list of pages${args?.categoryExtensions ?. 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 list_pages: 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.
list_pages 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_pages 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_pages. 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_pages is provided by the Chrome Devtools MCP server (shivamprasad99/chrome-devtools-mcp). 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 →