Get local variables and collections (design tokens). Filter by type or name to reduce token usage.
AI agents call figma_get_variables to retrieve information from Figma Unified without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though figma_get_variables only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Get local variables and collections (design tokens). Filter by type or name to reduce token usage. It is categorised as a Read tool in the Figma Unified MCP Server, which means it retrieves data without modifying state.
Register the Figma Unified MCP server in PolicyLayer and add a rule for figma_get_variables: 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 Unified. Nothing to install.
figma_get_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the figma_get_variables 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 figma_get_variables. 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.
figma_get_variables is provided by the Figma Unified MCP server (sso-ss/figma-unified-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.