get_node_info

THE RISK

Low Risk

Why get_node_info needs a policy

This tool retrieves node metadata from a Figma document without creating, modifying, deleting, or executing any changes. It is a pure read operation with no side effects on the design data. Low severity because the blast radius of misuse is limited to unauthorized information disclosure about design files.

From the tool's definition Tool description states 'Get detailed information about a specific node in Figma.' The verb 'Get' and context 'read, analyze, and export design data' from server description indicate retrieval without modification.

Documented attack patterns abuse exactly the kind of access get_node_info gives an agent:

POLICY

How to control get_node_info

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 get_node_info:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_node_info": {}
  }
}

get_node_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Figma MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Figma MCP Server tools

Read get_annotations get_annotations Read get_document_info Get detailed information about the current Figma document. Read get_instance_overrides Get instance overrides for a component instance. Read get_local_components Get all local components from the current Figma document. Read get_node_children Get all children node IDs from a specified node, including all nested levels. Read get_nodes_info Get detailed information about multiple nodes in Figma. Read get_reactions Get reactions (prototyping interactions) for nodes. Read get_selection Get information about the current selection in Figma.

All 15 Figma MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_node_info

What does the get_node_info tool do? +

Get detailed information about a specific node in Figma. It is categorised as a Read tool in the Figma MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_node_info? +

Register the Figma MCP Server MCP server in PolicyLayer and add a rule for get_node_info: 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.

What risk level is get_node_info? +

get_node_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_node_info? +

Yes. Add a rate_limit block to the get_node_info 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.

How do I block get_node_info completely? +

Set action: deny in the PolicyLayer policy for get_node_info. 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.

What MCP server provides get_node_info? +

get_node_info is provided by the Figma MCP Server MCP server (kdoronin/figma_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Figma MCP Server tool call.

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.

CHECK YOUR STACK →