Get a Figma file by key
AI agents call figma_get_file 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | string | — | Comma separated list of nodes that you care about in the document |
depth | number | — | Positive integer representing how deep into the document tree to traverse |
fileKey | string | — | The file key to use for the operation |
version | string | — | A specific version ID to get |
geometry | string | — | Set to "paths" to export vector data |
branch_data | boolean | — | Returns branch metadata for the requested file |
plugin_data | string | — | A comma separated list of plugin IDs and/or the string "shared" |
Parameters from the server's own tool schema.
This tool retrieves or queries a Figma file by its key identifier. It has no side effects—it does not create, modify, delete, or execute operations. It falls clearly into the Read category with low severity since file retrieval poses minimal risk of misuse in typical AI agent scenarios.
From the tool's definition Tool name 'figma_get_file' and description 'Get a Figma file by key' indicate a retrieval operation with no modification or deletion.
Attacks that exploit this kind of access
Get a Figma file by key. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.
figma_get_file accepts 7 parameters: ids, depth, fileKey, version, geometry, branch_data, plugin_data. The full parameter table on this page comes from the server's own tool schema.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for figma_get_file: 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.
figma_get_file 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 figma_get_file 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 figma_get_file. 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.
figma_get_file 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.
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 →