Low Risk

list_network_requests

List all requests for the currently selected page since the last navigation.

How to control list_network_requests ↓

What list_network_requests does on JS Reverse Strong MCP

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

Low Risk

Why list_network_requests needs a policy

This tool retrieves and displays network request data captured during browser observation. While it does not modify data, the medium severity reflects that network request logs may contain sensitive information (credentials, API keys, personal data in URLs/payloads) that an AI agent could exfiltrate.

From the tool's definition Tool description states 'List all requests for the currently selected page' — a retrieval operation with no modification or side effects. The verb 'list' confirms read-only behavior.

Documented attack patterns abuse exactly the kind of access list_network_requests gives an agent:

How to control list_network_requests

PolicyLayer is an MCP gateway — it sits between your AI agents and JS Reverse Strong MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_network_requests:

policy.json
{
  "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.

  1. Create a free account and register JS Reverse Strong MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_network_requests

What does the list_network_requests tool do? +

List all requests for the currently selected page since the last navigation. It is categorised as a Read tool in the JS Reverse Strong MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_network_requests? +

Register the JS Reverse Strong 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 Strong MCP. Nothing to install.

What risk level is list_network_requests? +

list_network_requests is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_network_requests? +

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.

How do I block list_network_requests completely? +

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.

What MCP server provides list_network_requests? +

list_network_requests is provided by the JS Reverse Strong MCP server (lwjjike/jsreverser-strong-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every JS Reverse Strong MCP tool call.

Start from JS Reverse Strong 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.

85 JS Reverse Strong MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.