Manage the stroke and its paints on Figma nodes. Each node has ONE stroke (with weight, alignment, caps, etc.) that can be painted with multiple Paint objects (solid colors, gradients, images, patterns). Returns YAML with stroke properties and paint layers.
AI agents use figma_strokes 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 or modifies design properties (stroke weight, alignment, caps, paint layers) on Figma nodes. These modifications are reversible—strokes can be edited, removed, or reset. The tool does not delete nodes or irreversibly destroy data, nor does it execute arbitrary code or commands. It fits the Write category as a design modification tool with measurable but recoverable impact.
From the tool's definition Tool description explicitly states it can 'manage the stroke and its paints on Figma nodes,' indicating modification of design properties. The server description confirms 'write access to Figma' and ability to 'modify... Figma designs programmatically.'
Documented attack patterns abuse exactly the kind of access figma_strokes 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_strokes:
{
"version": "1",
"default": "deny",
"tools": {
"figma_strokes": {
"limits": [
{
"counter": "figma_strokes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}figma_strokes 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.
Manage the stroke and its paints on Figma nodes. Each node has ONE stroke (with weight, alignment, caps, etc.) that can be painted with multiple Paint objects (solid colors, gradients, images, patterns). Returns YAML with stroke properties and paint layers. 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_strokes: 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_strokes 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_strokes 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_strokes. 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_strokes 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.