Add a user to an existing Kasm group
AI agents use add_user_to_group 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.
This tool modifies user attributes by adding membership to a group—a Write operation. It's reversible (groups can be modified), so not Destructive. The severity is medium because incorrect group assignments could grant unintended permissions within the Kasm infrastructure, but the action is non-destructive and confined to permission/access control scope rather than data loss or financial impact.
From the tool's definition Tool name 'add_user_to_group' and description 'Add a user to an existing Kasm group' indicate a modification operation that changes user group membership, which is reversible (user can be removed from group).
Attacks that exploit this kind of access
Add a user to an existing Kasm group. 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 add_user_to_group: 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.
add_user_to_group 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 add_user_to_group 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 add_user_to_group. 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.
add_user_to_group 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 →