set_stroke_color · Talk to Figma MCP: Risk & Policy

WHAT IT DOES

What set_stroke_color does on Talk to Figma MCP

AI agents use set_stroke_color to create or update resources in Talk to Figma MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Talk to Figma MCP environment.

WHY IT NEEDS A POLICY

Why set_stroke_color needs a policy

set_stroke_color modifies a visual property of a design node but does not delete data or trigger external code execution. The change is reversible—the stroke color can be changed again or reverted. This is a classic Write operation: updating design metadata.

From the tool's definition Tool description states 'Set the stroke color of a node in Figma', indicating modification of a design property.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_stroke_color Rate-limited

set_stroke_color 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_stroke_color": {
      "limits": [
        {
          "counter": "set_stroke_color_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Talk to Figma MCP, so you can run agents against it safely.

FAQ

Questions about set_stroke_color

What does the set_stroke_color tool do? +

Set the stroke color of a node in Figma. It is categorised as a Write tool in the Talk to Figma MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_stroke_color? +

Register the Talk to Figma MCP server in PolicyLayer and add a rule for set_stroke_color: 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 Talk to Figma MCP. Nothing to install.

What risk level is set_stroke_color? +

set_stroke_color is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_stroke_color? +

Yes. Add a rate_limit block to the set_stroke_color 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.

How do I block set_stroke_color completely? +

Set action: deny in the PolicyLayer policy for set_stroke_color. 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.

What MCP server provides set_stroke_color? +

set_stroke_color is provided by the Talk to Figma MCP server (pipethedev/talk-to-figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.