Generate semantic HTML from a node.
AI agents use figma_generate_html to create or update resources in Figma Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma Unified environment.
An AI agent can call figma_generate_html faster than any human can review — one bad instruction and it creates or modifies resources in Figma Unified by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Generate semantic HTML from a node. It is categorised as a Write tool in the Figma Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma Unified MCP server in PolicyLayer and add a rule for figma_generate_html: 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 Unified. Nothing to install.
figma_generate_html 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 figma_generate_html 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 figma_generate_html. 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.
figma_generate_html is provided by the Figma Unified MCP server (sso-ss/figma-unified-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.