AI agents call find_nodes_in_scenes to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
group | object | — | Filter by node group |
node_type | object | — | Filter by node type (e.g. "CharacterBody2D", "Timer") |
max_results | object | — | Max results (default: 100) |
signal_name | object | — | Filter scenes with this signal connection |
property_key | object | — | Filter by property key (e.g. "position", "script") |
property_value | object | — | Filter by property value (partial match, e.g. "player.gd") |
Parameters from the server's own tool schema.
This tool retrieves information about nodes matching specified criteria (type/property filters) across scenes in a Godot project. It performs a search query without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only discover unwanted information about scene structure, not cause state changes or execute arbitrary code.
From the tool's definition Tool description states 'Search nodes across scenes' - a query/search operation with no modification or execution of code. The verb 'find' and 'search' are characteristic of retrieval operations.
Attacks that exploit this kind of access
Search nodes across scenes by type/property. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_nodes_in_scenes accepts 6 parameters: group, node_type, max_results, signal_name, property_key, property_value. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for find_nodes_in_scenes: 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 Godot. Nothing to install.
find_nodes_in_scenes 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 find_nodes_in_scenes 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 find_nodes_in_scenes. 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.
find_nodes_in_scenes is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
find_nodes_in_scenes is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →