session.end
End an active session. Side effects: stops billing, runs host safety_restore, closes apps launched via app.launch. Always call when finished or abandoning — do not leave sessions open. Safe to call once; further observe/input on that session_id will fail.
This record as markdown: /tools/com-glasswarp-mcp-server/session.end.md
What session.end does on Glasswarp
AI agents invoke session.end to trigger actions in Glasswarp. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Session id returned by session.start |
Parameters from the server's own tool schema.
Why session.end is rated High
This tool executes consequential operations on a remote Windows PC system. While the primary purpose is cleanup, it actively triggers side effects (safety restoration, app closure, billing changes) on the host system. This constitutes an Execute category action rather than simple Read/Write, as it runs host-level operations.
From the tool's definition 'End an active session. Side effects: stops billing, runs host safety_restore, closes apps launched via app.launch.' — this tool triggers external operations (ending sessions, running safety_restore, closing applications) whose effects depend on the…
Attacks that exploit this kind of access
The rule that runs session.end safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Glasswarp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session.end, this is the rule to start with:
session.end 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Glasswarp, apply this rule, and every session.end call is checked against it from then on.
Questions about session.end
End an active session. Side effects: stops billing, runs host safety_restore, closes apps launched via app.launch. Always call when finished or abandoning — do not leave sessions open. Safe to call once; further observe/input on that session_id will fail. It is categorised as a Execute tool in the Glasswarp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
session.end accepts 1 parameter: session_id. Required: session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Glasswarp MCP server in PolicyLayer and add a rule for session.end: 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 Glasswarp. Nothing to install.
session.end 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.end 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.end. 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.end is provided by the Glasswarp MCP server (https://mcp.glasswarp.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Glasswarp, and thousands of servers like it.
Across the catalogue