Export the diagram to a file (PNG, SVG, or JSON).
AI agents use export_diagram to create or update resources in Flowchart MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Flowchart MCP environment.
This tool creates new data artifacts (exported files) but does not irreversibly destroy data or execute arbitrary code. It is a Write operation—creating/exporting data reversibly. Severity is low because misuse (e.g., exporting many files) has minimal blast radius; it consumes disk space but causes no data loss or financial harm.
From the tool's definition Tool exports diagrams to file formats (PNG, SVG, or JSON). While this creates output files, export operations are reversible—the exported files can be deleted, overwritten, or replaced without affecting the original diagram.
Attacks that exploit this kind of access
Export the diagram to a file (PNG, SVG, or JSON). It is categorised as a Write tool in the Flowchart MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Flowchart MCP server in PolicyLayer and add a rule for export_diagram: 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 Flowchart MCP. Nothing to install.
export_diagram 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_diagram 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_diagram. 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_diagram is provided by the Flowchart MCP server (zafer-liu/flowchart_mcp). 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 →