Update the text content of an existing FigJam sticky note.
AI agents use set_sticky_text 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.
The tool modifies text content within a FigJam sticky note, which is a standard write operation. It is reversible (text can be edited again), affects only the sticky note's content without deletion or financial impact, and does not execute external code or shell commands. The blast radius is minimal—an AI agent misuse would result in unwanted text changes that can be easily corrected.
From the tool's definition Tool description states 'Update the text content of an existing FigJam sticky note' — this is a direct modification operation that creates or changes data in a reversible manner.
Documented attack patterns abuse exactly the kind of access set_sticky_text 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 set_sticky_text:
{
"version": "1",
"default": "deny",
"tools": {
"set_sticky_text": {
"limits": [
{
"counter": "set_sticky_text_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_sticky_text 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.
Update the text content of an existing FigJam sticky note. 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 set_sticky_text: 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.
set_sticky_text 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_sticky_text 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_sticky_text. 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_sticky_text 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.