run_tshark_command · Tshark MCP: Risk & Policy

WHAT IT DOES

What run_tshark_command does on Tshark

AI agents invoke run_tshark_command 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 run_tshark_command needs a policy

This tool permits execution of arbitrary TShark commands whose effects depend on the arguments provided. TShark can read, write, and modify network data; capture live traffic; access system resources; and potentially interact with sensitive network state. While not inherently destructive (doesn't delete data by default), it enables code-like execution with external side effects on the network or file system.

From the tool's definition Tool explicitly named 'run_tshark_command' with description stating it 'Run[s] a TShark command with the given arguments.' TShark is a network protocol analyzer command-line tool that can execute arbitrary packet analysis operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_tshark_command Rate-limited

run_tshark_command 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": {
    "run_tshark_command": {
      "limits": [
        {
          "counter": "run_tshark_command_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 run_tshark_command

What does the run_tshark_command tool do? +

Run a TShark command with the given arguments. 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 run_tshark_command? +

Register the Tshark MCP server in PolicyLayer and add a rule for run_tshark_command: 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 run_tshark_command? +

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

Can I rate-limit run_tshark_command? +

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

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

run_tshark_command 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.