Scan for child nodes with specific types in the selected Figma node
AI agents call scan_nodes_by_types to retrieve information from Figma AI Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about nodes matching specific type filters within a Figma document. It performs no side effects, does not modify design assets, and is purely informational. Querying and listing operations are classified as Read, which carries low severity due to minimal risk of misuse.
From the tool's definition Tool description states it 'Scan for child nodes with specific types' — a retrieval operation with no modification, creation, or deletion of data. The verb 'scan' combined with 'for' indicates a query/search pattern.
Documented attack patterns abuse exactly the kind of access scan_nodes_by_types gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Figma AI Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for scan_nodes_by_types:
{
"version": "1",
"default": "deny",
"tools": {
"scan_nodes_by_types": {}
}
} scan_nodes_by_types 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.
Scan for child nodes with specific types in the selected Figma node. It is categorised as a Read tool in the Figma AI Bridge MCP Server, which means it retrieves data without modifying state.
Register the Figma AI Bridge MCP server in PolicyLayer and add a rule for scan_nodes_by_types: 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 AI Bridge. Nothing to install.
scan_nodes_by_types 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 scan_nodes_by_types 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 scan_nodes_by_types. 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.
scan_nodes_by_types is provided by the Figma AI Bridge MCP server (renfei-design/figma_ai_bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Figma AI 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.
64 Figma AI Bridge tools catalogued and risk-classified — across an index of 43,000+ MCP servers.