AI agents invoke session_stop to trigger actions in Kwin. 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.
session_stop triggers termination of a KWin session—an external operation whose effects depend on which session is targeted. While not destructive in the sense of deleting permanent data, it is irreversible in its immediate impact (halting a live session) and represents execution control over a system resource.
From the tool's definition Tool name 'session_stop' on a server that 'enables AI agents to automate Linux desktop GUI by launching and interacting with Wayland applications in isolated virtual KWin sessions.' The tool terminates an active session, which is an external operation with…
Documented attack patterns abuse exactly the kind of access session_stop gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kwin, and nothing reaches the server without passing your rules. This is the rule we recommend for session_stop:
{
"version": "1",
"default": "deny",
"tools": {
"session_stop": {
"limits": [
{
"counter": "session_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}session_stop 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.
Free to start. No card required.
session_stop. It is categorised as a Execute tool in the Kwin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kwin MCP server in PolicyLayer and add a rule for session_stop: 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 Kwin. Nothing to install.
session_stop 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 session_stop 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 session_stop. 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.
session_stop is provided by the Kwin MCP server (isac322/kwin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kwin, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
30 Kwin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.