remove_user_from_group · Kasm MCP Server v2 MCP

WHAT IT DOES

What remove_user_from_group does on Kasm MCP Server v2

AI agents use remove_user_from_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.

WHY IT NEEDS A POLICY

Why remove_user_from_group needs a policy

Removing a user from a group modifies group membership reversibly — the user can be re-added. This is a Write operation (modify/update), not Destructive since the user account itself is not deleted. Misuse could revoke access privileges, making severity medium.

From the tool's definition Remove a user from an existing Kasm group

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_user_from_group Rate-limited

remove_user_from_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_user_from_group": {
      "limits": [
        {
          "counter": "remove_user_from_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kasm MCP Server v2, so you can run agents against it safely.

FAQ

Questions about remove_user_from_group

What does the remove_user_from_group tool do? +

Remove a user from 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.

How do I enforce a policy on remove_user_from_group? +

Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for remove_user_from_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.

What risk level is remove_user_from_group? +

remove_user_from_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_user_from_group? +

Yes. Add a rate_limit block to the remove_user_from_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.

How do I block remove_user_from_group completely? +

Set action: deny in the PolicyLayer policy for remove_user_from_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.

What MCP server provides remove_user_from_group? +

remove_user_from_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.