Search for elements in a Figma file by type, name, etc.
AI agents call search-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.
This tool retrieves or searches for design elements within a Figma file without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the design or system state. The sibling tools (extract-text, get-comments, get-components, etc.) further confirm this server is focused on data retrieval rather than mutations or executions.
From the tool's definition Tool name 'search-file' combined with description 'Search for elements in a Figma file by type, name, etc.' indicates a query/retrieval operation with no modification or execution of external code.
Attacks that exploit this kind of access
Search for elements in a Figma file by type, name, etc. 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 search-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.
search-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 search-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 search-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.
search-file is provided by the Figma MCP Server MCP server (mohammeduvaiz/figma-mcp-server). 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 →