find_nodes_by_script
🔴 Game must be running. Find all nodes in the game that use a specific script
This record as markdown: /tools/keeveeg-godot-mcp/find-nodes-by-script.md
What find_nodes_by_script does on Godot
AI agents call find_nodes_by_script to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
script_path | string | Yes | Script file path to search for (e.g. 'res://scripts/enemy.gd') |
Parameters from the server's own tool schema.
Why find_nodes_by_script is rated Low
The tool performs a read-only search operation to locate nodes matching a criteria (script usage). It queries existing game data and returns results with no side effects, modifications, or code execution. This fits the Read category definition of retrieving or querying data without side effects.
From the tool's definition Tool description: 'Find all nodes in the game that use a specific script' - this is a query/search operation that retrieves information about nodes without modifying game state or executing code.
Attacks that exploit this kind of access
The rule that runs find_nodes_by_script safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_nodes_by_script, this is the rule to start with:
find_nodes_by_script is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every find_nodes_by_script call is checked against it from then on.
Questions about find_nodes_by_script
🔴 Game must be running. Find all nodes in the game that use a specific script. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_nodes_by_script accepts 1 parameter: script_path. Required: script_path. 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_by_script: 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_by_script 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_by_script 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_by_script. 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_by_script is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue