Check for circular references and validate dependencies
AI agents call validate_references 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.
This tool performs analysis and validation of existing data structures (references and dependencies) without creating, modifying, deleting, or executing external operations. It is purely informational—checking for circular references is a read-only diagnostic operation that reports on data integrity without altering state. No side effects or irreversible actions are possible.
From the tool's definition Tool name 'validate_references' and description 'Check for circular references and validate dependencies' indicate a validation/checking operation with no modification or destructive capability.
Documented attack patterns abuse exactly the kind of access validate_references gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_references:
{
"version": "1",
"default": "deny",
"tools": {
"validate_references": {}
}
}validate_references is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check for circular references and validate dependencies. 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 validate_references: 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.
validate_references 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 validate_references 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 validate_references. 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.
validate_references is provided by the Figma MCP Server MCP server (timholden/figma-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Figma MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 Figma MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.