AI agents use resize_node to create or update resources in MCP Figma — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Figma environment.
Resizing a node modifies design properties but is fully reversible—the original size can be restored. This is a Write operation (modifies data reversibly) rather than Execute (which would be for running arbitrary commands). Severity is medium because misuse could corrupt design work or waste time, but changes are easily undone and don't affect data outside Figma or cause permanent loss.
From the tool's definition Tool name 'resize_node' and description 'Resize a node in Figma' indicate modification of design element properties.
Attacks that exploit this kind of access
Resize a node in Figma. It is categorised as a Write tool in the MCP Figma MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Figma MCP server in PolicyLayer and add a rule for resize_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 MCP Figma. Nothing to install.
resize_node is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the resize_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.
Set action: deny in the PolicyLayer policy for resize_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.
resize_node is provided by the MCP Figma MCP server (yelowflash09/figma_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →