AI agents use merge_pcap_files 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.
Merging PCAP files is a write operation that creates new or modified data (combined packet capture files). The operation is reversible—the original files remain unchanged and the merged output can be discarded. While it modifies/creates artifacts, it does not execute arbitrary commands, delete irreversibly, or move funds.
From the tool's definition Tool name 'merge_pcap_files' indicates combining/merging PCAP packet capture files. Description is empty, limiting direct evidence, but the operation creates a modified/new PCAP artifact from source files.
Attacks that exploit this kind of access
merge_pcap_files. 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.
Register the Tshark MCP server in PolicyLayer and add a rule for merge_pcap_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 Tshark. Nothing to install.
merge_pcap_files 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 merge_pcap_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 merge_pcap_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.
merge_pcap_files 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.
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 →