Get version history of a Figma file
AI agents call figma_get_file_versions 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 |
|---|---|---|---|
after | number | — | A version ID for one of the versions in the history. Gets versions after this ID |
before | number | — | A version ID for one of the versions in the history. Gets versions before this ID |
fileKey | string | — | The file key to use for the operation |
page_size | number | — | The number of items returned in a page of the response |
Parameters from the server's own tool schema.
This tool queries and retrieves version history information from Figma, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any changes to files or data. The blast radius of misuse is minimal — an agent could only view historical version information, which does not expose sensitive operations or irreversible actions.
From the tool's definition Tool name and description: 'Get version history of a Figma file' — retrieves historical metadata about file versions without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Get version history of a Figma file. 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_versions accepts 4 parameters: after, before, fileKey, page_size. 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_versions: 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_versions 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_versions 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_versions. 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_versions 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 →