AI agents use create_connections to create or update resources in MCP Figma — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Figma environment.
This tool creates new connections between design nodes, which is a reversible modification to the Figma document. It does not execute arbitrary code, delete data, or move money. The severity is medium because misuse could create unwanted design changes requiring manual cleanup, but the changes are non-destructive and can be undone in Figma.
From the tool's definition Tool name 'create_connections' and description 'Create connections between nodes using the default connector style' indicate creation of new design elements (connections/connectors) in Figma, which modifies the design file.
Attacks that exploit this kind of access
Create connections between nodes using the default connector style. It is categorised as a Write tool in the MCP Figma MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Figma MCP server in PolicyLayer and add a rule for create_connections: 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 MCP Figma. Nothing to install.
create_connections 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_connections 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_connections. 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_connections is provided by the MCP Figma MCP server (yelowflash09/figma_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 →