Create connections between nodes using the default connector style
AI agents use create_connections to create or update resources in Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Talk to Figma MCP environment.
The tool creates new design connections in Figma, which is a write operation (reversible creation of data). It does not execute arbitrary code or trigger external operations (Execute), does not irreversibly delete data (Destructive), does not move money (Financial), and does not merely read data (Read).
From the tool's definition create_connections creates connections between nodes using the default connector style; this is a reversible modification operation that adds relational data to Figma designs without destroying or executing external code.
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 Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Talk to 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 Talk to Figma MCP. 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 Talk to Figma MCP server (pipethedev/talk-to-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 →