set_text_content · Claude Talk to Figma MCP: Risk & Policy

WHAT IT DOES

What set_text_content does on Claude Talk to Figma MCP

AI agents use set_text_content 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.

WHY IT NEEDS A POLICY

Why set_text_content needs a policy

This tool modifies text nodes in Figma designs, which is a reversible write operation. The modification could affect design documents and collaborative work, but is not irreversible (text can be changed again), does not delete data, does not execute code, and does not involve financial transactions.

From the tool's definition Tool description states 'Set the text content of an existing text node in Figma' — this modifies existing design data reversibly. Server description confirms it 'create[s], modify[s]... design elements in real-time.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_text_content Rate-limited

set_text_content 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_text_content": {
      "limits": [
        {
          "counter": "set_text_content_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 Claude Talk to Figma MCP, so you can run agents against it safely.

FAQ

Questions about set_text_content

What does the set_text_content tool do? +

Set the text content of an existing text node in Figma. 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.

How do I enforce a policy on set_text_content? +

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

What risk level is set_text_content? +

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

Can I rate-limit set_text_content? +

Yes. Add a rate_limit block to the set_text_content 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_text_content completely? +

Set action: deny in the PolicyLayer policy for set_text_content. 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_text_content? +

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