Create a workflow diagram / flowchart in Figma with shapes (start, end, process, decision, subprocess, note), arrows, labels, and automatic graph layout.
AI agents use create_workflow_diagram to create or update resources in Figma AI Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma AI Bridge environment.
The tool creates new design artifacts (workflow diagrams) within Figma, which is a reversible modification operation. While it modifies the design document, the changes can be undone/deleted, so it does not rise to Destructive. It is not Execute because it doesn't run arbitrary code or external processes—it simply constructs predefined diagram elements.
From the tool's definition Tool description states it creates workflow diagrams with shapes, arrows, and labels in Figma. The verb 'create' combined with the ability to add multiple design elements (shapes, arrows, labels) to a Figma document indicates data modification.
Documented attack patterns abuse exactly the kind of access create_workflow_diagram gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma AI Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for create_workflow_diagram:
{
"version": "1",
"default": "deny",
"tools": {
"create_workflow_diagram": {
"limits": [
{
"counter": "create_workflow_diagram_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_workflow_diagram 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 a workflow diagram / flowchart in Figma with shapes (start, end, process, decision, subprocess, note), arrows, labels, and automatic graph layout. It is categorised as a Write tool in the Figma AI Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for create_workflow_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 Figma AI Bridge. Nothing to install.
create_workflow_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 create_workflow_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 create_workflow_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.
create_workflow_diagram is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma AI Bridge, 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.
64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.