create_text
AI agents use create_text 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 new text elements in a Figma design file, modifying the document structure. It aligns with other creation tools on the server that add content to Figma projects. While reversible (text can be deleted), it constitutes a Write operation that changes persistent design state.
From the tool's definition Tool name 'create_text' combined with sibling tools like 'create_arc', 'create_circle', 'create_frame_in_figma', 'create_page' indicates design document creation/modification capabilities within Figma.
Attacks that exploit this kind of access
create_text. 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_text: 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_text 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_text 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_text. 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_text 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.
create_text is one line of Figma MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →