list_network_requests

What list_network_requests does on Js Reverse

AI agents call list_network_requests to retrieve information from Js Reverse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_network_requests is rated Low

This tool retrieves and queries network traffic data from the browser's DevTools, which is inherently a read-only operation. However, the severity is medium rather than low because network request data can include sensitive information (API keys, authentication tokens, PII, session identifiers), making this a valuable target for data exfiltration by a compromised agent, even though the tool itself performs no…

From the tool's definition Tool name 'list_network_requests' and description 'List all requests for the currently selected page' indicate a data retrieval operation with no modification or execution of external systems.

The rule that runs list_network_requests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_network_requests, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_network_requests": {}
  }
}

Questions about list_network_requests