AI agents use create_text to create or update resources in MCP Figma — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Figma environment.
This tool creates a new reversible asset in Figma (a text element). Creation is a Write operation—it modifies the design document but does not delete or irreversibly destroy content. While an agent could spam text elements or clutter a design, this is reversible via undo or deletion.
From the tool's definition Tool description states 'Create a new text element in Figma', which is a create operation that adds new data to the design document. The server description mentions 'element creation' and 'text replacement' as supported capabilities.
Attacks that exploit this kind of access
Create a new text element in Figma. It is categorised as a Write tool in the MCP Figma MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Figma 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 MCP Figma. 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 MCP Figma MCP server (yelowflash09/figma_mcp). 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 MCP Figma'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 →