AI agents use set_text_content 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 or modifies data (text in Figma designs) reversibly, fitting the Write category. Severity is medium because misuse could corrupt design content and affect collaboration, but changes are undoable and lack the irreversibility of Destructive actions or the code-execution risk of Execute actions. High confidence due to clear, explicit description of the modification operation.
From the tool's definition Tool name 'set_text_content' and description 'Set the text content of an existing text node in Figma' indicate modification of design data. The action is reversible (text can be changed again) and does not permanently destroy data or execute arbitrary code.
Attacks that exploit this kind of access
Set the text content of an existing text node 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 set_text_content: 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.
set_text_content 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 set_text_content 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 set_text_content. 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.
set_text_content 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.
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 →