List captured network requests (newest first-capped). Each row shows an #id usable with network_get_detail.
AI agents call network_get 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.
This tool retrieves and lists network request logs without side effects. It is a read-only operation that queries captured data. While the server as a whole performs undetectable web automation (potentially concerning), this specific tool merely inspects network activity that has already occurred, making it a Read category tool with low severity.
From the tool's definition Tool name 'network_get' and description 'List captured network requests' indicate retrieval/querying of already-captured network data with 'Each row shows an #id usable with network_get_detail' confirming it returns a list for inspection.
Documented attack patterns abuse exactly the kind of access network_get gives an agent:
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:
{
"version": "1",
"default": "deny",
"tools": {
"network_get": {}
}
}network_get 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 captured network requests (newest first-capped). Each row shows an #id usable with network_get_detail. It is categorised as a Read tool in the MCP Camoufox MCP Server, which means it retrieves data without modifying state.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for network_get: 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.
network_get 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 network_get 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 network_get. 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.
network_get 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.
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.