Remove entire project directory and all locally synced PCAP files. Use for full cleanup when analysis is complete. Does not affect GitHub repo. Uses GitHub credentials from MCP headers to determine project name, or accepts explicit project_name. Optional: project_name.
AI agents call wireshark_clean_project to permanently remove resources in Wireshark MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs irreversible deletion of local project directories and PCAP files. While it does not affect the GitHub repository (mitigating factor), the local deletion of analysis artifacts and synced files is a destructive action that cannot be reversed. An AI agent misusing this could destroy analysis work and forensic evidence.
From the tool's definition "Remove entire project directory and all locally synced PCAP files" — explicitly irreversible deletion of data. The tool description uses destructive language: 'Remove', 'cleanup', indicating data erasure that cannot be undone.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Remove entire project directory and all locally synced PCAP files. Use for full cleanup when analysis is complete. Does not affect GitHub repo. Uses GitHub credentials from MCP headers to determine project name, or accepts explicit project_name. Optional: project_name. It is categorised as a Destructive tool in the Wireshark MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Wireshark MCP Server MCP server in PolicyLayer and add a rule for wireshark_clean_project: 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.
wireshark_clean_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the wireshark_clean_project 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 wireshark_clean_project. 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.
wireshark_clean_project is provided by the Wireshark MCP Server MCP server (presidio-federal/wireshark-mcp-container). 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 →