list_pages

Get a list of pages${args?.categoryExtensions ?

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/list-pages.md

WHAT IT DOES

What list_pages does on Chrome Devtools

AI agents call list_pages 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.

RISK

Why list_pages is rated Low

This tool retrieves or lists data (pages in a Chrome DevTools context) with no side effects. It does not create, modify, delete, execute code, or move money. The Read category is appropriate for informational/query operations. Severity is low because listing pages presents minimal risk—it only exposes metadata about the browser state without enabling harmful actions directly.

From the tool's definition Tool name 'list_pages' and description 'Get a list of pages' indicate a retrieval operation that queries the state of open browser pages without modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_pages 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 list_pages, this is the rule to start with:

list_pages Allowed

list_pages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_pages": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every list_pages call is checked against it from then on.

FAQ

Questions about list_pages

What does the list_pages tool do? +

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.

How do I enforce a policy on list_pages? +

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.

What risk level is list_pages? +

list_pages is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_pages? +

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.

How do I block list_pages completely? +

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.

What MCP server provides list_pages? +

list_pages 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.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →