session.start
Start a metered desktop session on a USABLE rig from rigs.list. Side effects: begins wall-clock billing, shows an on-screen “API session active” indicator, enables observe/input until session.end. Idle sessions auto-end after ~15 minutes. Always call session.end when done or abandoning. Do not ca...
This record as markdown: /tools/com-glasswarp-mcp-server/session.start.md
What session.start does on Glasswarp
AI agents invoke session.start 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 |
|---|---|---|---|
rig_id | string | Yes | Rig id from rigs.list (must be online with api_access_enabled) |
Parameters from the server's own tool schema.
Why session.start is rated High
This tool triggers substantial side effects beyond simple data retrieval: it allocates resources (a physical desktop rig), initiates billing, activates on-screen indicators, and enables input actions on a real machine.
From the tool's definition The tool "Start a metered desktop session" with "Side effects: begins wall-clock billing, shows an on-screen 'API session active' indicator, enables observe/input until session.end." This grants control over a real Windows PC with input capabilities (click,…
Attacks that exploit this kind of access
The rule that runs session.start 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.start, this is the rule to start with:
session.start 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.start call is checked against it from then on.
Questions about session.start
Start a metered desktop session on a USABLE rig from rigs.list. Side effects: begins wall-clock billing, shows an on-screen “API session active” indicator, enables observe/input until session.end. Idle sessions auto-end after ~15 minutes. Always call session.end when done or abandoning. Do not call if no USABLE rig exists. Returns session_id and Live View URL (owner console login required). 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.start accepts 1 parameter: rig_id. Required: rig_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.start: 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.start 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.start 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.start. 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.start 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