Create and manage design annotations using Figma native API - annotations are stored directly on nodes and auto-cleanup when nodes are deleted
AI agents use figma_annotations to create or update resources in Figma Mcp Write — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma Mcp Write environment.
This tool creates and modifies annotations on design nodes, which is a reversible write operation. While it doesn't delete data or execute code, it modifies Figma project state. The severity is medium because incorrect annotations could confuse design workflows, but the changes are easily correctable and don't result in data loss or financial impact.
From the tool's definition Tool description states 'Create and manage design annotations' and server description indicates 'write access to Figma...enabling AI agents to create, modify, and manage Figma designs programmatically.' The word 'Create and manage' indicates reversible…
Documented attack patterns abuse exactly the kind of access figma_annotations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma Mcp Write, and nothing reaches the server without passing your rules. This is the rule we recommend for figma_annotations:
{
"version": "1",
"default": "deny",
"tools": {
"figma_annotations": {
"limits": [
{
"counter": "figma_annotations_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}figma_annotations stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create and manage design annotations using Figma native API - annotations are stored directly on nodes and auto-cleanup when nodes are deleted. It is categorised as a Write tool in the Figma Mcp Write MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma Mcp Write MCP server in PolicyLayer and add a rule for figma_annotations: 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 Write. Nothing to install.
figma_annotations 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_annotations 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_annotations. 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_annotations is provided by the Figma Mcp Write MCP server (oo/figma-mcp-write-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma Mcp Write, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
24 Figma Mcp Write tools catalogued and risk-classified — across an index of 43,000+ MCP servers.