Set a gradient fill on a node in Figma. Supports linear, radial, angular, and diamond gradients. Replaces all existing fills (same behavior as set_fill_color).
AI agents use set_gradient 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 modifies (writes) design attributes in Figma by setting or replacing gradient fills on nodes. The changes are reversible—users can undo the action or apply different gradients. While it affects visual design properties, it does not delete data irreversibly, execute arbitrary code, or create financial obligations.
From the tool's definition Tool description states it 'Set[s] a gradient fill on a node' and 'Replaces all existing fills', which are reversible modifications to design properties.
Documented attack patterns abuse exactly the kind of access set_gradient 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_gradient:
{
"version": "1",
"default": "deny",
"tools": {
"set_gradient": {
"limits": [
{
"counter": "set_gradient_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_gradient 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.
Set a gradient fill on a node in Figma. Supports linear, radial, angular, and diamond gradients. Replaces all existing fills (same behavior as set_fill_color). 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_gradient: 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_gradient 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_gradient 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_gradient. 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_gradient 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.