Destroy an existing Kasm session.
AI agents call destroy_kasm_session to permanently remove resources in Kasm MCP Server v2 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'destroy' verb and the irreversible nature of terminating a containerized session (which cannot be easily recovered) places this in the Destructive category. While not deleting persistent data, destroying an active session is a non-reversible action that disrupts user operations.
From the tool's definition Tool name contains 'destroy' and description states 'Destroy an existing Kasm session' — this terminates a session irreversibly, terminating active user work and potentially losing unsaved state.
Attacks that exploit this kind of access
Destroy an existing Kasm session. It is categorised as a Destructive tool in the Kasm MCP Server v2 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for destroy_kasm_session: 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 Kasm MCP Server v2. Nothing to install.
destroy_kasm_session 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 destroy_kasm_session 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 destroy_kasm_session. 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.
destroy_kasm_session is provided by the Kasm MCP Server v2 MCP server (roguedev-ai/kasm-mcp-server-v2). 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 →