Restore the canvas from a previously saved named snapshot
AI agents use restore_snapshot to create or update resources in Excalidraw MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Excalidraw MCP Server environment.
The tool modifies canvas state by loading and applying a snapshot, making it a Write operation rather than Read. It is not Destructive because the original snapshot is preserved and the operation is theoretically reversible (via another snapshot restore).
From the tool's definition 'Restore the canvas from a previously saved named snapshot' — this operation reverts the canvas state to a prior version, modifying the current diagram irreversibly by overwriting all unsaved changes with historical content.
Attacks that exploit this kind of access
Restore the canvas from a previously saved named snapshot. It is categorised as a Write tool in the Excalidraw MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Excalidraw MCP Server MCP server in PolicyLayer and add a rule for restore_snapshot: 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 Excalidraw MCP Server. Nothing to install.
restore_snapshot 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 restore_snapshot 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 restore_snapshot. 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.
restore_snapshot is provided by the Excalidraw MCP Server MCP server (kakacoding1/mcp_excalidraw). 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 →