Gets a network request by URL. You can get all requests by calling ${listNetworkRequests.name}.
AI agents call get_network_request 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 performs passive inspection of network traffic that has already occurred. It retrieves request metadata without creating, modifying, executing, or deleting anything. The blast radius of misuse is limited to potential information disclosure of network requests (headers, payloads, responses), which is a low-severity read operation.
From the tool's definition Tool 'get_network_request' retrieves network request data by URL with no modification capability. Description explicitly states it 'Gets a network request', a read-only operation.
Attacks that exploit this kind of access
Gets a network request by URL. You can get all requests by calling ${listNetworkRequests.name}. 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 get_network_request: 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.
get_network_request 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 get_network_request 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 get_network_request. 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.
get_network_request 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 →