capture_process · Tshark MCP: Risk & Policy

WHAT IT DOES

What capture_process does on Tshark

AI agents invoke capture_process to trigger actions in Tshark. 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 capture_process needs a policy

The tool name suggests it captures or manages a capture process, likely involving live network packet capture via TShark. Live network capture is an Execute-category action as it triggers external operations (sniffing network interfaces). The description is empty, lowering confidence, but given the server context and sibling tools, this is almost certainly related to live packet capture execution.

From the tool's definition Tool name 'capture_process' on a server that supports 'live capture' functionality; sibling tools include 'capture_live' and 'capture_and_decrypt'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

capture_process Rate-limited

capture_process 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": {
    "capture_process": {
      "limits": [
        {
          "counter": "capture_process_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 Tshark, so you can run agents against it safely.

FAQ

Questions about capture_process

What does the capture_process tool do? +

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

How do I enforce a policy on capture_process? +

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

What risk level is capture_process? +

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

Can I rate-limit capture_process? +

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

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

capture_process is provided by the Tshark MCP server (ouonet/tshark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.