Create a sticky note in a FigJam board. Sticky notes are the primary way to add text content in FigJam.
AI agents use create_sticky to create or update resources in Claude Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Talk to Figma MCP environment.
This tool writes/creates new data (a sticky note) in FigJam, making it a Write action. The severity is low because sticky notes are discrete, non-destructive additions to a collaborative whiteboard that can be easily deleted or edited by any user. There is no financial impact, no code execution, and no data destruction.
From the tool's definition create_sticky creates a sticky note in a FigJam board, which adds text content without irreversible deletion or modification of existing design assets. The action is reversible and creates new, isolated content.
Documented attack patterns abuse exactly the kind of access create_sticky gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Talk to Figma MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_sticky:
{
"version": "1",
"default": "deny",
"tools": {
"create_sticky": {
"limits": [
{
"counter": "create_sticky_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Create a sticky note in a FigJam board. Sticky notes are the primary way to add text content in FigJam. It is categorised as a Write tool in the Claude Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Talk to Figma MCP server in PolicyLayer and add a rule for 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 Claude Talk to Figma MCP. Nothing to install.
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 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 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.
create_sticky is provided by the Claude Talk to Figma MCP server (arinspunk/claude-talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Talk to Figma MCP, 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.
93 Claude Talk to Figma MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.