Pause a running Kasm session to free up resources.
AI agents invoke pause_kasm_session 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.
Pausing a session triggers an external operational state change on a containerized desktop session. It is not a simple read, nor does it irreversibly delete data. The session is suspended (not destroyed), making it reversible and thus not Destructive. It executes an action against live infrastructure, fitting the Execute category. Misuse could disrupt active user sessions, warranting medium severity.
From the tool's definition Pause a running Kasm session to free up resources
Attacks that exploit this kind of access
Pause a running Kasm session to free up resources. 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.
Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for pause_kasm_session: 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.
pause_kasm_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pause_kasm_session 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 pause_kasm_session. 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.
pause_kasm_session 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 →