AI agents call list_network_requests to retrieve information from Camoufox Reverse without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists network request information—a non-destructive, side-effect-free data query operation. Despite the server's anti-detection and bot-bypass capabilities (which enable circumventing security controls), the list_network_requests function itself only reads/observes network activity without modifying, executing, or deleting anything.
From the tool's definition Tool name 'list_network_requests' clearly indicates retrieval/enumeration of network request data with no modification capability. Server context shows tools for 'network interception' and 'dynamic debugging', consistent with read-only inspection.
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 Camoufox Reverse, 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_network_requests. It is categorised as a Read tool in the Camoufox Reverse MCP Server, which means it retrieves data without modifying state.
Register the Camoufox 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 Camoufox Reverse. 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 Camoufox Reverse MCP server (whitenightshadow/camoufox-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.