Extract files from HTTP, DICOM, IMF, SMB, or TFTP traffic in a pcap file.
AI agents call tshark_extract_files 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.
While the tool operates on network data, it reads and exports files from already-captured traffic without modifying or deleting the underlying pcap data. The extraction of files from network traffic does not constitute irreversible data loss or external system modification—it retrieves information that was already captured.
From the tool's definition Tool description states it 'Extract[s] files from HTTP, DICOM, IMF, SMB, or TFTP traffic in a pcap file.' The word 'extract' indicates retrieval of data from existing packet captures, with no modification of the pcap or network state.
Attacks that exploit this kind of access
Extract files from HTTP, DICOM, IMF, SMB, or TFTP traffic in a pcap file. 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_extract_files: 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_extract_files 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_extract_files 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_extract_files. 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_extract_files 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 →