update_kasm_user · Kasm MCP Server v2 MCP: Risk & Policy

WHAT IT DOES

What update_kasm_user does on Kasm MCP Server v2

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

WHY IT NEEDS A POLICY

Why update_kasm_user needs a policy

The tool updates user account properties, which is a Write operation—it creates or modifies data reversibly without permanent destruction. Severity is high because unauthorized user modifications in a containerized desktop infrastructure could grant improper access, create backdoor accounts, or escalate privileges.

From the tool's definition Tool name 'update_kasm_user' indicates modification of user records. Server description states it provides 'user management' capabilities. Sibling tools include create_kasm_user and delete_kasm_user, confirming this server handles user lifecycle operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_kasm_user Rate-limited

update_kasm_user 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": {
    "update_kasm_user": {
      "limits": [
        {
          "counter": "update_kasm_user_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 update_kasm_user

What does the update_kasm_user tool do? +

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

How do I enforce a policy on update_kasm_user? +

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

What risk level is update_kasm_user? +

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

Can I rate-limit update_kasm_user? +

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

How do I block update_kasm_user completely? +

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

What MCP server provides update_kasm_user? +

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