create_line
AI agents use create_line 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 line in Figma is a reversible write operation that modifies a design file by adding a new shape element. It does not delete data (not Destructive), execute arbitrary code (not Execute), or commit financial obligations (not Financial). While the description is empty (lowering confidence slightly), the tool name and sibling context strongly indicate it creates design artifacts, fitting the Write category.
From the tool's definition Tool named 'create_line' on Figma MCP Server, with sibling tools like 'create_rectangle', 'create_circle', 'create_arc', 'create_polygon', and 'create_frame_in_figma' that all create/modify design objects.
Attacks that exploit this kind of access
create_line. 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_line: 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_line 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_line 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_line. 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_line 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 →