List all requests for the currently selected page since the last navigation.
AI agents call list_network_requests to retrieve information from ReverseCraft 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 pure data retrieval and inspection of existing network traffic. While the server context involves browser automation and debugging capabilities, this specific tool merely lists network requests without modifying, executing, or deleting anything. It is information-gathering only, making it a Read operation with low severity due to the minimal risk of misuse (viewing network request metadata).
From the tool's definition The tool 'list_network_requests' retrieves and queries network request data that has already occurred on the page, with a description explicitly stating it 'List all requests' - a passive observation action with no side effects.
Documented attack patterns abuse exactly the kind of access list_network_requests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReverseCraft DevTools MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_network_requests:
{
"version": "1",
"default": "deny",
"tools": {
"list_network_requests": {}
}
} list_network_requests is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all requests for the currently selected page since the last navigation. It is categorised as a Read tool in the ReverseCraft DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the ReverseCraft DevTools MCP server in PolicyLayer and add a rule for list_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 ReverseCraft DevTools MCP. Nothing to install.
list_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 list_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 list_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.
list_network_requests is provided by the ReverseCraft DevTools MCP server (reverse-craft/rc-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReverseCraft DevTools MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
46 ReverseCraft DevTools MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.