List network requests for the currently selected page. By default this includes requests retained from before the current navigation (set includePreservedRequests=false to limit to the current navigation only). Results are sorted newest-first and include request start time plus duration. By defau...
AI agents call list_network_requests to retrieve information from JS Reverse MCP 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 data from the browser's DevTools protocol without any ability to modify, delete, or trigger actions. It is purely informational and read-only, appropriate for debugging and analysis purposes.
From the tool's definition Tool description states it 'List network requests' and 'returns' data about requests with filtering and pagination options. No mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List network requests for the currently selected page. By default this includes requests retained from before the current navigation (set includePreservedRequests=false to limit to the current navigation only). Results are sorted newest-first and include request start time plus duration. By default returns the 20 most recent requests; use pageSize/pageIdx to paginate. Narrow the list with filters: methods (HTTP verb, e.g. [. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse 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 JS Reverse 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 JS Reverse MCP server (zhizhuodemao/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.