demos.list
List showcase run contracts (id, title, install, command). Read-only catalog — does NOT start a session, touch a rig, or run solvers. Use when the user asks for Minesweeper/Mona Lisa/Paint demos or you need the glasswarp-demo command. Prefer demos.get for one full card. For ad-hoc UI work use rig...
This record as markdown: /tools/com-glasswarp-mcp-server/demos.list.md
What demos.list does on Glasswarp
AI agents call demos.list 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 |
|---|---|---|---|
format | string | — | Response format: markdown (default) or json |
Parameters from the server's own tool schema.
Why demos.list is rated Low
Purely lists demo contracts with no side effects or modifications.
From the tool's definition Read-only catalog — does NOT start a session, touch a rig
Attacks that exploit this kind of access
The rule that runs demos.list 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 demos.list, this is the rule to start with:
demos.list 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 demos.list call is checked against it from then on.
Questions about demos.list
List showcase run contracts (id, title, install, command). Read-only catalog — does NOT start a session, touch a rig, or run solvers. Use when the user asks for Minesweeper/Mona Lisa/Paint demos or you need the glasswarp-demo command. Prefer demos.get for one full card. For ad-hoc UI work use rigs.list → session.start → screen.observe instead. It is categorised as a Read tool in the Glasswarp MCP Server, which means it retrieves data without modifying state.
demos.list accepts 1 parameter: format. 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 demos.list: 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.
demos.list 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 demos.list 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 demos.list. 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.
demos.list 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