Get detailed information about specific Figma nodes by their IDs. Returns node properties including type, position, size, fills, strokes, and more. TIP: Use figma_search_nodes or figma_get_children FIRST to find node IDs efficiently, then use this tool only for nodes you need full details on.
AI agents call figma_get_nodes to retrieve information from Figma MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
figma_get_nodes retrieves and queries node data from Figma documents without side effects. It returns information only (type, position, size, fills, strokes) and does not create, modify, delete, or execute operations. This is a straightforward Read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Get[s] detailed information about specific Figma nodes' and 'Returns node properties' — purely retrieval operations with no modification, deletion, or execution of arbitrary operations. The tip reinforces this as a lookup utility.
Documented attack patterns abuse exactly the kind of access figma_get_nodes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for figma_get_nodes:
{
"version": "1",
"default": "deny",
"tools": {
"figma_get_nodes": {}
}
}figma_get_nodes 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 detailed information about specific Figma nodes by their IDs. Returns node properties including type, position, size, fills, strokes, and more. TIP: Use figma_search_nodes or figma_get_children FIRST to find node IDs efficiently, then use this tool only for nodes you need full details on. It is categorised as a Read tool in the Figma MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the Figma MCP Bridge MCP server in PolicyLayer and add a rule for figma_get_nodes: 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 Bridge. Nothing to install.
figma_get_nodes 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 figma_get_nodes 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 figma_get_nodes. 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.
figma_get_nodes is provided by the Figma MCP Bridge MCP server (magic-spells/figma-mcp-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma MCP Bridge, 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.
88 Figma MCP Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.