create_vector
AI agents use create_vector 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.
This tool creates vector shapes/elements in Figma, which is a reversible modification operation. It fits the Write category (creates or modifies data reversibly). Severity is medium because misuse could clutter designs or interfere with user workflows, but changes can be undone in Figma. Confidence is 0.75 due to the empty description, though the naming pattern and sibling context strongly suggest vector creation.
From the tool's definition Tool name 'create_vector' combined with sibling tools like 'create_arc', 'create_circle', 'create_frame_in_figma', 'create_line', 'create_polygon' which clearly perform creation operations in Figma. The tool description is empty, reducing certainty.
Attacks that exploit this kind of access
create_vector. 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_vector: 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_vector 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_vector 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_vector. 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_vector 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 →