create_kasm_user
AI agents use create_kasm_user to create or update resources in Kasm MCP Server v2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kasm MCP Server v2 environment.
The tool creates user accounts, which is a Write operation that modifies system state (adds a new identity/principal to the system). While reversible via delete_kasm_user, account creation has high severity because it expands access surface, can persist indefinitely if not tracked, and may be leveraged for unauthorized access or privilege escalation within Kasm infrastructure.
From the tool's definition Tool name 'create_kasm_user' explicitly indicates creation of a new user account. Server context shows this is part of Kasm Workspaces user management infrastructure. Description is empty, limiting precision but the name is unambiguous about intent.
Attacks that exploit this kind of access
create_kasm_user. It is categorised as a Write tool in the Kasm MCP Server v2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for create_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.
create_kasm_user 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 create_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 create_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.
create_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 →