Low Risk

list_network_requests

list_network_requests

How to control list_network_requests ↓

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

Low Risk

This tool retrieves historical or current network request metadata from a debugging session—a read-only operation with no side effects. However, the context of 'reverse engineering purposes' and network interception capabilities elevates severity from low to medium, as intercepted network data could include sensitive credentials, API keys, or proprietary business logic.

From the tool's definition Tool name 'list_network_requests' combined with server context (Chrome DevTools Protocol, network interception, debugging) indicates retrieval of network request data.

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 MiniApp CDP 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 MiniApp CDP 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.

Go deeper

What does the list_network_requests tool do? +

list_network_requests. It is categorised as a Read tool in the MiniApp CDP MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_network_requests? +

Register the MiniApp CDP 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 MiniApp CDP 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 MiniApp CDP MCP server (zhizhuodemao/miniapp-cdp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MiniApp CDP MCP tool call.

Deterministic rules across all 18 MiniApp CDP MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

18 MiniApp CDP MCP tools catalogued and risk-classified — across an index of 42,500+ 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.