figma_move_node · Figma Unified MCP: Risk & Policy

WHAT IT DOES

What figma_move_node does on Figma Unified

AI agents use figma_move_node to create or update resources in Figma Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma Unified environment.

WHY IT NEEDS A POLICY

Why figma_move_node needs a policy

An AI agent can call figma_move_node faster than any human can review — one bad instruction and it creates or modifies resources in Figma Unified by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

figma_move_node Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "figma_move_node": {
      "limits": [
        {
          "counter": "figma_move_node_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Figma Unified, so you can run agents against it safely.

FAQ

Questions about figma_move_node

What does the figma_move_node tool do? +

Move a node to a new position. It is categorised as a Write tool in the Figma Unified 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_move_node? +

Register the Figma Unified MCP server in PolicyLayer and add a rule for figma_move_node: 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.

What risk level is figma_move_node? +

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

Can I rate-limit figma_move_node? +

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

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

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