Low Risk

get_variables

List all variable collections and their variables in the current Figma file. Returns collections with their modes and variables.

How to control get_variables ↓

What get_variables does on Claude Talk to Figma MCP

AI agents call get_variables to retrieve information from Claude Talk to Figma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_variables needs a policy

This tool queries and retrieves variable metadata from a Figma file without creating, modifying, deleting, or executing any operations. It has read-only semantics and produces no side effects beyond returning information. Blast radius is minimal as the worst outcome is exposure of design system variable definitions, which are typically non-sensitive metadata.

From the tool's definition Tool description states 'List all variable collections and their variables' which is a retrieval operation with no modification or side effects. The verb 'List' and the phrase 'Returns collections' indicate data retrieval only.

Documented attack patterns abuse exactly the kind of access get_variables gives an agent:

How to control get_variables

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 get_variables:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_variables": {}
  }
}

get_variables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Talk to Figma MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_variables

What does the get_variables tool do? +

List all variable collections and their variables in the current Figma file. Returns collections with their modes and variables. It is categorised as a Read tool in the Claude Talk to Figma MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_variables? +

Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for 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 Claude Talk to Figma MCP. Nothing to install.

What risk level is get_variables? +

get_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_variables? +

Yes. Add a rate_limit block to the 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.

How do I block get_variables completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides get_variables? +

get_variables 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.

Enforce policy on every Claude Talk to Figma MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.