create_circle
AI agents use create_circle to create or update resources in Figma MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Server environment.
Creating a circle in Figma modifies the document by adding a new design element, which is a reversible operation (the element can be deleted). This fits the Write category - it creates/modifies data without being irreversible. Severity is medium because modifying design documents could impact collaborative work, though the effect is easily undoable.
From the tool's definition Tool name 'create_circle' combined with sibling tools like 'create_arc', 'create_frame_in_figma', 'create_rectangle', 'create_line', 'create_polygon', and 'create_page' all follow a pattern of creating/adding design elements in Figma.
Attacks that exploit this kind of access
create_circle. It is categorised as a Write tool in the Figma MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for create_circle: 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 MCP Server. Nothing to install.
create_circle 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 create_circle 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 create_circle. 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.
create_circle is provided by the Figma MCP Server MCP server (sichang824/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 →