Fetches two Figma file versions and reports added, removed, and modified nodes by comparing names, types, geometry, fills, and style properties.
AI agents call diff_versions to retrieve information from Figma Spec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though diff_versions only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Fetches two Figma file versions and reports added, removed, and modified nodes by comparing names, types, geometry, fills, and style properties. It is categorised as a Read tool in the Figma Spec MCP Server, which means it retrieves data without modifying state.
Register the Figma Spec MCP server in PolicyLayer and add a rule for diff_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 Spec. Nothing to install.
diff_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 diff_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 diff_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.
diff_versions is provided by the Figma Spec MCP server (zaferdace/figma-spec-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.