Save the current canvas state as a named snapshot for later restoration.
AI agents use snapshot_scene to create or update resources in tldraw MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tldraw MCP Server environment.
This tool creates a named snapshot (a new saved state) of the canvas, which is a reversible write operation. It does not delete or overwrite data, execute code, or move money. The snapshot can be restored later, implying the operation is not destructive. Severity is medium because misuse could clutter storage or create misleading snapshots, but the blast radius is limited.
From the tool's definition Save the current canvas state as a named snapshot for later restoration
Attacks that exploit this kind of access
Save the current canvas state as a named snapshot for later restoration. It is categorised as a Write tool in the tldraw MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tldraw MCP Server MCP server in PolicyLayer and add a rule for snapshot_scene: 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 tldraw MCP Server. Nothing to install.
snapshot_scene is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the snapshot_scene 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 snapshot_scene. 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.
snapshot_scene is provided by the tldraw MCP Server MCP server (mihai-codes/tldraw-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →