figma_post_comment_reaction · Figma MCP Server MCP

WHAT IT DOES

What figma_post_comment_reaction does on Figma MCP Server

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

PARAMETERS

Parameter	Type	Required	Description
`emoji`	string	—	The emoji to react with
`fileKey`	string	—	The file key to use for the operation
`commentId`	string	—	The ID of the comment to add a reaction to

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why figma_post_comment_reaction needs a policy

This tool creates a new reaction (a form of metadata) associated with an existing comment. It modifies state reversibly—reactions can be removed via delete operations (as evidenced by the sibling tool figma_delete_comment_reaction). This is clearly a Write operation.

From the tool's definition Tool name 'figma_post_comment_reaction' and description 'Add a reaction to a comment' indicate a POST operation that creates/modifies data (adds a reaction). The word 'post' and 'add' indicate content creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

figma_post_comment_reaction Rate-limited

figma_post_comment_reaction 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": {
    "figma_post_comment_reaction": {
      "limits": [
        {
          "counter": "figma_post_comment_reaction_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 Figma MCP Server, so you can run agents against it safely.

FAQ

Questions about figma_post_comment_reaction

What does the figma_post_comment_reaction tool do? +

Add a reaction to a comment. It is categorised as a Write tool in the Figma MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does figma_post_comment_reaction accept? +

figma_post_comment_reaction accepts 3 parameters: emoji, fileKey, commentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on figma_post_comment_reaction? +

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

What risk level is figma_post_comment_reaction? +

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

Can I rate-limit figma_post_comment_reaction? +

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

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

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