AI agents use create_reference to create or update resources in Figma MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Server environment.
The tool creates new data structures (variable references) that modify the state of Figma files reversibly. While it doesn't directly change variable values, creating references can affect design system behavior and component linking. This is a Write category action rather than Execute because it modifies structured data through a specific API rather than running arbitrary code.
From the tool's definition Tool name 'create_reference' and description 'Create a reference between variables' indicate a creation operation that modifies Figma variable relationships. This is a write operation that establishes new connections between design system variables.
Documented attack patterns abuse exactly the kind of access create_reference gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_reference:
{
"version": "1",
"default": "deny",
"tools": {
"create_reference": {
"limits": [
{
"counter": "create_reference_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_reference 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 reference between variables. It is categorised as a Write tool in the Figma MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for create_reference: 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 MCP Server. Nothing to install.
create_reference 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_reference 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_reference. 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_reference is provided by the Figma MCP Server MCP server (timholden/figma-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Figma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Figma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.