find_node_references
Find all references to a node across scenes and scripts
This record as markdown: /tools/keeveeg-godot-mcp/find-node-references.md
What find_node_references does on Godot
AI agents call find_node_references 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 |
|---|---|---|---|
query | string | Yes | Node path or name to search for |
Parameters from the server's own tool schema.
Why find_node_references is rated Low
This tool retrieves information about node references without modifying, creating, deleting, or executing any operations. It is a read-only analysis tool similar to a search or grep function across a Godot project. The blast radius is minimal as it cannot cause side effects or unintended modifications.
From the tool's definition The tool 'find_node_references' performs a search operation to 'Find all references to a node across scenes and scripts'. This is a query/search operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs find_node_references 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_node_references, this is the rule to start with:
find_node_references 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_node_references call is checked against it from then on.
Questions about find_node_references
Find all references to a node across scenes and scripts. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_node_references accepts 1 parameter: query. Required: query. 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_node_references: 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_node_references 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_node_references 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_node_references. 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_node_references 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