List all requests for the currently selected page since the last navigation.
AI agents call list_network_requests to retrieve information from Chrome DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays network request metadata (timing, URL, status, etc.) from the browser's network log. It is purely observational—no data is modified, deleted, or executed as a result of calling it. The low severity reflects minimal blast radius: an agent listing network requests could gain insights into page behavior but cannot directly harm systems or data.
From the tool's definition Tool name 'list_network_requests' and description 'List all requests for the currently selected page since the last navigation' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
List all requests for the currently selected page since the last navigation. It is categorised as a Read tool in the Chrome DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the Chrome DevTools MCP server in PolicyLayer and add a rule for list_network_requests: 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.
list_network_requests 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_network_requests 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_network_requests. 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_network_requests is provided by the Chrome DevTools MCP server (shay5555-gif/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 →