Medium Risk

figma_push_variables

Write design tokens back to Figma as Variables via the Figma REST API. Creates or updates variable collections.

Part of the Ui MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@forgespace/ui-mcp Write Risk 2/5

AI agents use figma_push_variables to create or modify resources in Ui. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call figma_push_variables repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Ui.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

io-github-forge-space-ui-mcp.yaml
tools:
  figma_push_variables:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Ui policy for all 38 tools.

Tool Name figma_push_variables
Category Write
MCP Server Ui MCP Server
Risk Level Medium

View all 38 tools →

Agents calling write-class tools like figma_push_variables have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the figma_push_variables tool do? +

Write design tokens back to Figma as Variables via the Figma REST API. Creates or updates variable collections.. It is categorised as a Write tool in the Ui MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on figma_push_variables? +

Add a rule in your Intercept YAML policy under the tools section for figma_push_variables. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ui MCP server.

What risk level is figma_push_variables? +

figma_push_variables is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit figma_push_variables? +

Yes. Add a rate_limit block to the figma_push_variables rule in your Intercept 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 figma_push_variables completely? +

Set action: deny in the Intercept policy for figma_push_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 figma_push_variables? +

figma_push_variables is provided by the Ui MCP server (@forgespace/ui-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Ui

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.