AI agents call get_node to retrieve information from Figma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Figma node data (likely a specific design element or component node). It performs no modifications, deletions, or code execution. The sibling tools (get_components, get_workflow) and server purpose (allowing agents to 'access' Figma) confirm a read-only data retrieval function. Low severity because misuse would only expose design data without destructive or operational impact.
From the tool's definition Tool is named 'get_node' and exists alongside 'get_components' and 'get_workflow' in a Figma access server. The server description emphasizes 'access' to Figma files, pages, components, and prototypes—all read operations.
Documented attack patterns abuse exactly the kind of access get_node gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma, and nothing reaches the server without passing your rules. This is the rule we recommend for get_node:
{
"version": "1",
"default": "deny",
"tools": {
"get_node": {}
}
}get_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_node. It is categorised as a Read tool in the Figma MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP server in PolicyLayer and add a rule for get_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. Nothing to install.
get_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 get_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 get_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.
get_node is provided by the Figma MCP server (jayzeedesign/figma-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma, 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.
3 Figma tools catalogued and risk-classified — across an index of 43,000+ MCP servers.