Get all annotations in the current document or specific node
AI agents call get_annotations 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 retrieves annotation metadata from a Figma document without side effects. It is a read-only operation that queries existing data. No data is created, modified, deleted, or executed. The low severity reflects minimal blast radius: an AI agent misusing this tool can only access design annotations, not alter designs or trigger external actions.
From the tool's definition Tool name is 'get_annotations' and description states 'Get all annotations in the current document or specific node' — both explicitly indicate retrieval/query with no modification, creation, or deletion of data.
Attacks that exploit this kind of access
Get all annotations in the current document or specific node. 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_annotations: 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_annotations 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_annotations 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_annotations. 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_annotations 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 →