get_elements
AI agents call get_elements to retrieve information from Figma MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name indicates a retrieval operation ('get'). In Figma's context, fetching design elements is a non-destructive read operation with no side effects. The empty description reduces confidence slightly, but the naming convention and peer tools (all write/analyze operations) strongly suggest this is a query/fetch operation. Blast radius is minimal—reading design data poses no integrity or operational risk.
From the tool's definition Tool name 'get_elements' follows the 'get' pattern, which is standard for retrieval operations. Context of sibling tools (create_*, add_comment, analyze_*) and Figma API suggest this retrieves design elements without modification.
Attacks that exploit this kind of access
get_elements. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for get_elements: 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.
get_elements 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_elements 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_elements. 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_elements is provided by the Figma MCP Server MCP server (sichang824/mcp-figma). 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 →