Import elements from a .excalidraw JSON file or raw JSON data
AI agents use import_scene 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.
This tool creates or modifies the canvas state by importing elements, making it a Write operation. It is not Read (does not merely retrieve data), not Execute (does not run arbitrary code or commands), not Destructive (the import can be undone via undo or canvas clearing), and not Financial.
From the tool's definition Tool description states it 'Import elements from a .excalidraw JSON file or raw JSON data,' which adds/modifies the canvas by loading external elements.
Attacks that exploit this kind of access
Import elements from a .excalidraw JSON file or raw JSON data. 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 import_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 Excalidraw MCP Server. Nothing to install.
import_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 import_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 import_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.
import_scene 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 →