update_node · Figmad MCP: Risk & Policy

WHAT IT DOES

What update_node does on Figmad

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

WHY IT NEEDS A POLICY

Why update_node needs a policy

This tool creates or modifies data reversibly within Figma designs. While it changes design state, these modifications are undoable through Figma's standard undo functionality and do not permanently destroy data.

From the tool's definition Tool description explicitly states it can "Update properties of an existing Figma node. Can modify position, size, text, visibility, and more." The term "Update" combined with modifiable properties (position, size, text, visibility) indicates reversible…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_node Rate-limited

update_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": {
    "update_node": {
      "limits": [
        {
          "counter": "update_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 Figmad, so you can run agents against it safely.

FAQ

Questions about update_node

What does the update_node tool do? +

Update properties of an existing Figma node. Can modify position, size, text, visibility, and more. It is categorised as a Write tool in the Figmad MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_node? +

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

What risk level is update_node? +

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

Can I rate-limit update_node? +

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

Set action: deny in the PolicyLayer policy for update_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 update_node? +

update_node is provided by the Figmad MCP server (toro1221/figmad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.