List and export HTTP objects (files) from a pcap capture
AI agents call tshark_export_objects to retrieve information from Wireshark MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads a pre-existing pcap capture file and extracts/lists HTTP objects from it. It does not capture live traffic, modify data, execute commands, or perform destructive operations. However, it can expose sensitive file contents transmitted over HTTP, hence medium severity due to potential data disclosure.
From the tool's definition "List and export HTTP objects (files) from a pcap capture" — reads and extracts data from an existing pcap file
Attacks that exploit this kind of access
List and export HTTP objects (files) from a pcap capture. It is categorised as a Read tool in the Wireshark MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wireshark MCP Server MCP server in PolicyLayer and add a rule for tshark_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 Wireshark MCP Server. Nothing to install.
tshark_export_objects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the tshark_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.
Set action: deny in the PolicyLayer policy for tshark_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.
tshark_export_objects is provided by the Wireshark MCP Server MCP server (schwarztim/sec-wireshark-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →