AI agents call add_figma_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.
The tool appears to fetch and load a Figma file's data into the AI context for viewing/analysis. This is a read/retrieval operation with no apparent side effects on the Figma file itself. Severity is low because it only reads design data.
From the tool's definition 'Add a Figma file to your context' — loads/retrieves a Figma file into the assistant's context window
Documented attack patterns abuse exactly the kind of access add_figma_file 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 add_figma_file:
{
"version": "1",
"default": "deny",
"tools": {
"add_figma_file": {}
}
} add_figma_file 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.
Add a Figma file to your context. 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 add_figma_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.
add_figma_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 add_figma_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 add_figma_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.
add_figma_file is provided by the Figma MCP Server MCP server (matthewdailey/figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 Figma MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.