get_network_request
Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/get-network-request.md
What get_network_request does on Chrome DevTools MCP
AI agents call get_network_request to retrieve information from Chrome DevTools MCP 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_request is rated Low
This tool retrieves and queries network request data from Chrome DevTools Network panel for inspection and debugging purposes. It does not execute code, modify state, delete data, or trigger external operations. The capability to inspect network requests is informational and poses minimal security risk in the context of an AI agent; the worst misuse would be information disclosure about intercepted network traffic.
From the tool's definition Tool description states 'Gets a network request' — a retrieval operation with no modification or execution. The verb 'Gets' and the passive data retrieval nature confirm this is a Read operation that inspects network traffic without side effects.
Attacks that exploit this kind of access
The rule that runs get_network_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_network_request, this is the rule to start with:
get_network_request 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 MCP, apply this rule, and every get_network_request call is checked against it from then on.
Questions about get_network_request
Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. 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 (anirbandz/chrome_mcp_devtool). 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