Exports a draw.io diagram XML to an SVG or PNG file.
AI agents use export_drawio to create or update resources in Drawio Engineering — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Drawio Engineering environment.
This tool creates or generates new output files (SVG/PNG exports) from diagram data. While the underlying diagram is not modified, the tool produces new persistent artifacts in the file system. This is a Write operation (creates files), not a Read operation (which would only retrieve data without side effects).
From the tool's definition Exports a draw.io diagram XML to an SVG or PNG file - creates new files (SVG or PNG) from existing diagram data
Documented attack patterns abuse exactly the kind of access export_drawio gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Drawio Engineering, and nothing reaches the server without passing your rules. This is the rule we recommend for export_drawio:
{
"version": "1",
"default": "deny",
"tools": {
"export_drawio": {
"limits": [
{
"counter": "export_drawio_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_drawio 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.
Exports a draw.io diagram XML to an SVG or PNG file. It is categorised as a Write tool in the Drawio Engineering MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Drawio Engineering MCP server in PolicyLayer and add a rule for export_drawio: 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 Drawio Engineering. Nothing to install.
export_drawio 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 export_drawio 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 export_drawio. 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.
export_drawio is provided by the Drawio Engineering MCP server (rfingadam/drawio-engineering-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Drawio Engineering, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Drawio Engineering tools catalogued and risk-classified — across an index of 43,000+ MCP servers.