AI agents call get_network_requests to retrieve information from Rn Debug without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries network request/response/error data from a debug session without creating, modifying, deleting, or executing any operations. It is purely informational—fetching historical buffered network events for inspection. The cursor-based pagination mechanism further confirms it is a safe read operation with no side effects.
From the tool's definition Tool name is "get_network_requests" and description states "Read buffered network request/response/error events using cursor-based pagination." The explicit use of "Read" and retrieval of buffered events with no modification capabilities indicates a read-only…
Attacks that exploit this kind of access
Read buffered network request/response/error events using cursor-based pagination. It is categorised as a Read tool in the Rn Debug MCP Server, which means it retrieves data without modifying state.
Register the Rn Debug MCP server in PolicyLayer and add a rule for get_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 Rn Debug. Nothing to install.
get_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 get_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 get_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.
get_network_requests is provided by the Rn Debug MCP server (rn-debug-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 →