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

Agent View of the PolicyLayer registry record for `session.end`. HTML page: https://policylayer.com/tools/com-glasswarp-mcp-server/session.end

## Facts

- Tool: `session.end`
- Server: Glasswarp (`https://mcp.glasswarp.com/mcp`) — https://policylayer.com/tools/com-glasswarp-mcp-server.md
- Homepage: https://github.com/glasswarp/mcp-server
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `session_id` | string | yes | Session id returned by session.start |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "session.end",
    "arguments": {
      "session_id": "<session_id>"
    }
  }
}
```

## 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 own 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…"

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Glasswarp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "session.end": {
      "limits": [
        {
          "counter": "session.end_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Glasswarp (15)

- `app.launch` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/app.launch.md
- `input.click_target` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.click-target.md
- `input.click_xy` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.click-xy.md
- `input.drag` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.drag.md
- `input.scroll` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.scroll.md
- `input.send_actions` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.send-actions.md
- `input.send_keys` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.send-keys.md
- `input.type_text` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/input.type-text.md
- `session.start` — Execute — https://policylayer.com/tools/com-glasswarp-mcp-server/session.start.md
- `demos.get` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/demos.get.md
- `demos.list` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/demos.list.md
- `rigs.list` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/rigs.list.md
- `screen.observe` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/screen.observe.md
- `session.live_view` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/session.live-view.md
- `session.status` — Read — https://policylayer.com/tools/com-glasswarp-mcp-server/session.status.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-glasswarp-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-glasswarp-mcp-server