get_network_response
Get detailed response data for a specific network request. Args: request_id: ID of the network request Returns: Detailed response data including body content
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-network-response.md
What get_network_response does on Chrome Devtools
AI agents call get_network_response 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.
Why get_network_response is rated Low
This tool passively queries network data that has already been captured by the browser's DevTools. While it can expose sensitive information in response bodies (headers, tokens, credentials, etc.), the operation itself is read-only with no side effects.
From the tool's definition Tool 'get_network_response' retrieves and returns 'detailed response data including body content' for a network request. The description uses retrieval language ("get", "returns") with no modification, creation, deletion, or execution of external systems.
Attacks that exploit this kind of access
The rule that runs get_network_response 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 get_network_response, this is the rule to start with:
get_network_response is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every get_network_response call is checked against it from then on.
Questions about get_network_response
Get detailed response data for a specific network request. Args: request_id: ID of the network request Returns: Detailed response data including body content. 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 get_network_response: 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.
get_network_response 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_response 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_response. 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_response is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). 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