Create multiple Excalidraw elements at once. For arrows, use startElementId/endElementId to bind arrows to shapes — Excalidraw auto-routes to element edges. Assign custom id to shapes so arrows can reference them.
AI agents use batch_create_elements 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 new diagram elements (shapes, arrows) in an Excalidraw drawing. While it modifies state, the changes are reversible (elements can be deleted), so it falls under Write rather than Destructive. The blast radius is medium because an agent could clutter or obscure a diagram with unwanted elements, but the damage can be easily undone.
From the tool's definition Tool description states it creates 'multiple Excalidraw elements at once', which is a create operation. The verb 'Create' in the tool name and the phrase 'Create multiple' in the description confirm this is a write operation that modifies the diagram by…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_create_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Excalidraw MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_create_elements:
{
"version": "1",
"default": "deny",
"tools": {
"batch_create_elements": {
"limits": [
{
"counter": "batch_create_elements_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_create_elements stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create multiple Excalidraw elements at once. For arrows, use startElementId/endElementId to bind arrows to shapes — Excalidraw auto-routes to element edges. Assign custom id to shapes so arrows can reference them. 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 batch_create_elements: 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.
batch_create_elements 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 batch_create_elements 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 batch_create_elements. 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.
batch_create_elements is provided by the Excalidraw MCP Server MCP server (yctimlin/mcp_excalidraw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 26 Excalidraw MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
26 Excalidraw MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.