AI agents call view_node 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 and displays thumbnail images of design elements. It has no side effects, does not modify data, and does not execute code or trigger external operations. The blast radius of misuse is minimal - an attacker could enumerate design nodes to gather information about a Figma project, but cannot alter designs or access sensitive data beyond what the authenticated user already has permission to view.
From the tool's definition Tool description states 'Get a thumbnail for a specific node in a Figma file' - retrieves visual data without modification.
Documented attack patterns abuse exactly the kind of access view_node 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 view_node:
{
"version": "1",
"default": "deny",
"tools": {
"view_node": {}
}
}view_node 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.
Get a thumbnail for a specific node in 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.
Register the Figma MCP Server MCP server in PolicyLayer and add a rule for view_node: 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.
view_node 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 view_node 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 view_node. 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.
view_node 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.