execute_kasm_command · Kasm MCP Server v2 MCP: Risk & Policy

WHAT IT DOES

What execute_kasm_command does on Kasm MCP Server v2

AI agents invoke execute_kasm_command to trigger actions in Kasm MCP Server v2. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_kasm_command needs a policy

This tool runs arbitrary commands within a Kasm containerized session. Command execution is inherently an Execute category risk because the blast radius depends entirely on what command is passed as an argument—an agent could execute commands that compromise the container, exfiltrate data, or pivot to other infrastructure.

From the tool's definition Tool name is 'execute_kasm_command' and description states 'Execute a command in a Kasm session.' This directly indicates code/command execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_kasm_command Rate-limited

execute_kasm_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_kasm_command": {
      "limits": [
        {
          "counter": "execute_kasm_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 execute_kasm_command

What does the execute_kasm_command tool do? +

Execute a command in a Kasm session. It is categorised as a Execute tool in the Kasm MCP Server v2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_kasm_command? +

Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for execute_kasm_command: 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 execute_kasm_command? +

execute_kasm_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_kasm_command? +

Yes. Add a rate_limit block to the execute_kasm_command 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 execute_kasm_command completely? +

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

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