Low Risk

network_get_detail

Full request + response detail (headers and text body) for one captured request.

How to control network_get_detail ↓

What network_get_detail does on MCP Camoufox

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

Low Risk

Why network_get_detail needs a policy

This tool queries captured network data to retrieve request/response information. While it is read-only with no direct side effects, the severity is elevated from 'low' to 'medium' because: (1) the parent server explicitly bypasses bot detection and enables undetectable web automation for potentially unauthorized scraping, and (2) access to full request/response bodies (especially headers) could expose sensitive…

From the tool's definition Tool retrieves 'Full request + response detail (headers and text body)' for captured network traffic. The verb 'get_detail' and description indicate data retrieval with no modification or execution.

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

How to control network_get_detail

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "network_get_detail": {}
  }
}

network_get_detail 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 MCP Camoufox — 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 network_get_detail

What does the network_get_detail tool do? +

Full request + response detail (headers and text body) for one captured request. It is categorised as a Read tool in the MCP Camoufox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on network_get_detail? +

Register the MCP Camoufox MCP server in PolicyLayer and add a rule for network_get_detail: 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 MCP Camoufox. Nothing to install.

What risk level is network_get_detail? +

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

Can I rate-limit network_get_detail? +

Yes. Add a rate_limit block to the network_get_detail 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 network_get_detail completely? +

Set action: deny in the PolicyLayer policy for network_get_detail. 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 network_get_detail? +

network_get_detail is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Camoufox tool call.

Start from MCP Camoufox, 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.

102 MCP Camoufox 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.