Low Risk

network_capture_full

Capture network requests with response bodies (capped). Actions: start, stop, getLogs, clear. Bodies over maxBodyBytes are omitted with reason=

How to control network_capture_full ↓

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

Low Risk

This tool captures and retrieves network traffic including response bodies, which is fundamentally a Read/monitoring operation. However, it carries medium severity because it can intercept sensitive data (auth tokens, credentials, API responses) passing through the browser. The 'clear' action is minor and reversible. No code execution or data modification is performed.

From the tool's definition Capture network requests with response bodies (capped). Actions: start, stop, getLogs, clear.

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

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

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

network_capture_full 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 OpenChrome — 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 network_capture_full tool do? +

Capture network requests with response bodies (capped). Actions: start, stop, getLogs, clear. Bodies over maxBodyBytes are omitted with reason=. It is categorised as a Read tool in the OpenChrome MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on network_capture_full? +

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

What risk level is network_capture_full? +

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

Can I rate-limit network_capture_full? +

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

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

network_capture_full is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenChrome tool call.

Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

106 OpenChrome 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.