Get the response body for a specific request by its requestId
AI agents call network_get_response_body to retrieve information from CDP-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves already-captured network response data from Chrome DevTools. It queries and returns information without modifying state, creating resources, executing code, deleting data, or moving money. The worst outcome of misuse is unauthorized reading of sensitive response bodies (e.g., API secrets, user data), which is a confidentiality risk but not a high-impact execution or destruction risk.
From the tool's definition Tool name is 'network_get_response_body' and description states it 'Get[s] the response body for a specific request by its requestId' — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the response body for a specific request by its requestId. It is categorised as a Read tool in the CDP-MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CDP-MCP Server MCP server in PolicyLayer and add a rule for network_get_response_body: 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 CDP-MCP Server. Nothing to install.
network_get_response_body 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 network_get_response_body 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 network_get_response_body. 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.
network_get_response_body is provided by the CDP-MCP Server MCP server (jekyll-001/cdp-mcp-server). 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 →