session.live_view
Return the console Live View URL (≈60fps) for the rig owner to watch and intervene. Read-only for the agent — does not grant the API key console access. Offer on long or sensitive tasks. Owner must be signed into Glasswarp; API keys alone cannot open the player.
This record as markdown: /tools/com-glasswarp-mcp-server/session.live-view.md
What session.live_view does on Glasswarp
AI agents call session.live_view to retrieve information from Glasswarp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Active session id |
Parameters from the server's own tool schema.
Why session.live_view is rated Low
This tool retrieves a URL for live viewing purposes only. It has no capability to modify, execute, or delete anything. The explicit "read-only" designation and requirement for owner authentication to actually use the URL (not just receive it) confirm this is a benign information-retrieval operation with minimal security risk.
From the tool's definition Tool description explicitly states "Return the console Live View URL" and "Read-only for the agent". The description emphasizes it does not grant API key console access and requires owner authentication.
Attacks that exploit this kind of access
The rule that runs session.live_view 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.live_view, this is the rule to start with:
session.live_view is read-only, so it stays allowed. 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.live_view call is checked against it from then on.
Questions about session.live_view
Return the console Live View URL (≈60fps) for the rig owner to watch and intervene. Read-only for the agent — does not grant the API key console access. Offer on long or sensitive tasks. Owner must be signed into Glasswarp; API keys alone cannot open the player. It is categorised as a Read tool in the Glasswarp MCP Server, which means it retrieves data without modifying state.
session.live_view 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.live_view: 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.live_view is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the session.live_view 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.live_view. 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.live_view 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.
This server
Across the catalogue