Delete a pentest session and all its evidence
AI agents call session_delete to permanently remove resources in Kali MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes pentest sessions and associated evidence, which cannot be recovered. This is a destructive operation that removes data irreversibly. While the blast radius is somewhat constrained to pentest artifacts rather than production systems, the loss of evidence and session data could have significant consequences for security assessments, compliance, and incident investigation.
From the tool's definition 'Delete a pentest session and all its evidence' — the tool irreversibly removes data (session and evidence) with no undo mechanism.
Documented attack patterns abuse exactly the kind of access session_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kali MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for session_delete:
{
"version": "1",
"default": "deny",
"hide": [
"session_delete"
]
}session_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a pentest session and all its evidence. It is categorised as a Destructive tool in the Kali MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kali MCP Server MCP server in PolicyLayer and add a rule for session_delete: 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 Kali MCP Server. Nothing to install.
session_delete 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 session_delete 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 session_delete. 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.
session_delete is provided by the Kali MCP Server MCP server (k3nn3dy-ai/kali-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kali MCP Server, 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.
36 Kali MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.