FigJam: create a sticky note. Default size is fixed (240×240); width/height are not configurable. Text is set via the embedded sublayer (font auto-loaded). Note: the author name and visibility are auto-populated by Figma from the active user — they cannot be set programmatically.
AI agents use figma_create_sticky to create or update resources in Figma MCP Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Figma MCP Bridge environment.
This tool creates new content (a sticky note) in a Figma/FigJam document, making it a Write operation. It is reversible (the sticky can be deleted), so it does not qualify as Destructive. The severity is medium because while creating unwanted sticky notes is annoying and could clutter a design document, the impact is limited to a single artifact and easily undone.
From the tool's definition Tool creates a sticky note in FigJam, which adds new content to the Figma document. The description explicitly states 'create a sticky note' and mentions setting text via sublayers, confirming this creates new data.
Documented attack patterns abuse exactly the kind of access figma_create_sticky gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for figma_create_sticky:
{
"version": "1",
"default": "deny",
"tools": {
"figma_create_sticky": {
"limits": [
{
"counter": "figma_create_sticky_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}figma_create_sticky 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.
FigJam: create a sticky note. Default size is fixed (240×240); width/height are not configurable. Text is set via the embedded sublayer (font auto-loaded). Note: the author name and visibility are auto-populated by Figma from the active user — they cannot be set programmatically. It is categorised as a Write tool in the Figma MCP Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Figma MCP Bridge MCP server in PolicyLayer and add a rule for figma_create_sticky: 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 Bridge. Nothing to install.
figma_create_sticky 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_create_sticky 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_create_sticky. 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_create_sticky is provided by the Figma MCP Bridge MCP server (magic-spells/figma-mcp-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma MCP Bridge, 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.
88 Figma MCP Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.