Export packets from a pcap file to a JSON file at output_path.
AI agents use export_json to create or update resources in Mcp Wireshark — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Wireshark environment.
This tool performs a reversible write operation that creates or overwrites a JSON file with exported packet data. It does not delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial). While it modifies the filesystem, the impact is limited to creating an output file from already-captured network data.
From the tool's definition Tool description states 'Export packets from a pcap file to a JSON file at output_path' - this creates or modifies a file on the filesystem. The verb 'export' combined with explicit output file specification indicates file creation/writing.
Documented attack patterns abuse exactly the kind of access export_json gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Wireshark, and nothing reaches the server without passing your rules. This is the rule we recommend for export_json:
{
"version": "1",
"default": "deny",
"tools": {
"export_json": {
"limits": [
{
"counter": "export_json_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} export_json 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.
Free to start. No card required.
Export packets from a pcap file to a JSON file at output_path. It is categorised as a Write tool in the Mcp Wireshark MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Wireshark MCP server in PolicyLayer and add a rule for export_json: 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 Mcp Wireshark. Nothing to install.
export_json is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_json 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.
Set action: deny in the PolicyLayer policy for export_json. 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.
export_json is provided by the Mcp Wireshark MCP server (khuynh22/mcp-wireshark). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Wireshark, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Mcp Wireshark tools catalogued and risk-classified — across an index of 43,000+ MCP servers.