Get Figma Prototyping Reactions from multiple nodes. CRITICAL: The output MUST be processed using the
AI agents call get_reactions to retrieve information from Talk to Figma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves reaction metadata from Figma design nodes. It performs a read-only operation with no side effects—it does not create, modify, delete, or execute any external operations. The 'get' prefix and 'from multiple nodes' retrieval pattern confirm this is a data retrieval function.
From the tool's definition Tool name 'get_reactions' and description indicate retrieval of Figma Prototyping Reactions data from nodes with no modification capability.
Attacks that exploit this kind of access
Get Figma Prototyping Reactions from multiple nodes. CRITICAL: The output MUST be processed using the. It is categorised as a Read tool in the Talk to Figma MCP MCP Server, which means it retrieves data without modifying state.
Register the 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 Talk to Figma MCP. Nothing to install.
get_reactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_reactions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →