Low Risk

get_reactions

Read all prototype interactions (reactions) from a node in Figma. Useful for debugging and inspecting existing interactions.

How to control get_reactions ↓

What get_reactions does on Claude Talk to Figma MCP

AI agents call get_reactions to retrieve information from Claude Talk to Figma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_reactions needs a policy

The tool retrieves and queries existing prototype interaction data from a Figma node. It performs no creation, modification, deletion, or execution of external operations. The word 'Read' in the description and the purpose of 'inspecting' confirm this is a read-only operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description explicitly states 'Read all prototype interactions (reactions)' and 'inspecting existing interactions' — pure information retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_reactions gives an agent:

How to control get_reactions

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 get_reactions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_reactions": {}
  }
}

get_reactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Talk to Figma MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_reactions

What does the get_reactions tool do? +

Read all prototype interactions (reactions) from a node in Figma. Useful for debugging and inspecting existing interactions. It is categorised as a Read tool in the Claude Talk to Figma MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_reactions? +

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

get_reactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_reactions? +

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

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

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

Enforce policy on every Claude Talk to Figma MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.