export_objects · Tshark MCP: Risk & Policy

WHAT IT DOES

What export_objects does on Tshark

AI agents use export_objects to create or update resources in Tshark — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tshark environment.

WHY IT NEEDS A POLICY

Why export_objects needs a policy

An AI agent can call export_objects faster than any human can review — one bad instruction and it creates or modifies resources in Tshark by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_objects Rate-limited

export_objects stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_objects": {
      "limits": [
        {
          "counter": "export_objects_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 export_objects

What does the export_objects tool do? +

export_objects. It is categorised as a Write tool in the Tshark MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_objects? +

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

export_objects is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_objects? +

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

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

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