Delete a user from the Kasm system.
AI agents call delete_kasm_user 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.
Deleting a user is an irreversible action that permanently removes user credentials, access permissions, and associated metadata from the system. This cannot be undone without restoring from backups. The action has significant blast radius: revoked access for legitimate users, potential service disruption, and loss of audit trails.
From the tool's definition Tool name is 'delete_kasm_user' and description states 'Delete a user from the Kasm system.' The verb 'delete' combined with permanent removal of a user account indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a user from the Kasm system. 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 delete_kasm_user: 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.
delete_kasm_user 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 delete_kasm_user 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 delete_kasm_user. 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.
delete_kasm_user 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 →