Set the corner radius of a node in Figma
AI agents use set_corner_radius to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.
This tool modifies design styling properties (corner radius) of Figma nodes, which is a Write operation—it changes data but is fully reversible by setting a different corner radius value. The impact is limited to design aesthetics within a single Figma document, affecting only the visual appearance of a node.
From the tool's definition Tool name 'set_corner_radius' and description 'Set the corner radius of a node in Figma' indicate modification of design element properties. This is a reversible change to existing design nodes.
Attacks that exploit this kind of access
Set the corner radius of a node in Figma. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for set_corner_radius: 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.
set_corner_radius 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 set_corner_radius 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 set_corner_radius. 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.
set_corner_radius is provided by the Claude Talk to Figma MCP server (stranyer/claude-mcp-figma). 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 →