configure_network_capture · WebControl MCP: Risk & Policy

WHAT IT DOES

What configure_network_capture does on WebControl

AI agents invoke configure_network_capture to trigger actions in WebControl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why configure_network_capture needs a policy

Based on the server context (headless browser automation) and the sibling tool 'get_network_capture' and 'clear_network_capture', this tool likely configures network traffic interception/capture settings within browser sessions. Configuration of network capture is an Execute-level action as it modifies runtime behavior of the browser automation environment and could intercept sensitive data.

From the tool's definition Tool name 'configure_network_capture' on a server that performs browser automation; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

configure_network_capture Rate-limited

configure_network_capture stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "configure_network_capture": {
      "limits": [
        {
          "counter": "configure_network_capture_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WebControl, so you can run agents against it safely.

FAQ

Questions about configure_network_capture

What does the configure_network_capture tool do? +

configure_network_capture. It is categorised as a Execute tool in the WebControl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on configure_network_capture? +

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

What risk level is configure_network_capture? +

configure_network_capture is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit configure_network_capture? +

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

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

configure_network_capture is provided by the WebControl MCP server (matansht/webcontrol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.