Create a connector (arrow or line) in FigJam. Connectors can link two existing nodes by ID, or connect arbitrary canvas positions. Use this to draw flow arrows between stickies, shapes, etc.
AI agents use create_connector to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.
This tool creates new design elements (connectors/arrows) in a Figma file, which modifies the document state. This is a Write operation because connectors are additive, visually reversible changes that can be undone or deleted. It does not execute arbitrary code (Execute), permanently delete data (Destructive), involve financial transactions (Financial), or perform side-effect-dependent external operations.
From the tool's definition Tool description states 'Create a connector (arrow or line) in FigJam' and 'draw flow arrows between stickies, shapes, etc.' The verb 'Create' and action of drawing new design elements indicates data creation that is reversible (connectors can be deleted).
Documented attack patterns abuse exactly the kind of access create_connector gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Talk to Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_connector:
{
"version": "1",
"default": "deny",
"tools": {
"create_connector": {
"limits": [
{
"counter": "create_connector_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_connector 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 connector (arrow or line) in FigJam. Connectors can link two existing nodes by ID, or connect arbitrary canvas positions. Use this to draw flow arrows between stickies, shapes, etc. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for create_connector: 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 Claude Talk to Figma MCP. Nothing to install.
create_connector 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_connector 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_connector. 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_connector is provided by the Claude Talk to Figma MCP server (arinspunk/claude-talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Talk to Figma MCP, 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.
93 Claude Talk to Figma MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.