session.status
Fetch session metadata: status, host, mode, created_at, action_count, billed_minutes. Read-only — no input side effects. Use to tell the user about metered time or confirm the session is still active before more actions.
This record as markdown: /tools/com-glasswarp-mcp-server/session.status.md
What session.status does on Glasswarp
AI agents call session.status 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 | Session id from session.start |
Parameters from the server's own tool schema.
Why session.status is rated Low
This tool purely queries and returns session metadata without side effects. It performs observation/status checking, which is the definition of a Read operation. The explicit 'read-only' language and absence of any modification capabilities make this low-severity with high confidence.
From the tool's definition Tool description explicitly states 'Read-only — no input side effects' and lists only metadata retrieval operations: 'status, host, mode, created_at, action_count, billed_minutes'.
Attacks that exploit this kind of access
The rule that runs session.status 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.status, this is the rule to start with:
session.status 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.status call is checked against it from then on.
Questions about session.status
Fetch session metadata: status, host, mode, created_at, action_count, billed_minutes. Read-only — no input side effects. Use to tell the user about metered time or confirm the session is still active before more actions. It is categorised as a Read tool in the Glasswarp MCP Server, which means it retrieves data without modifying state.
session.status 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.status: 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.status 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.status 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.status. 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.status 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