find_script_references
Find all scenes and nodes that use a specific script
This record as markdown: /tools/keeveeg-godot-mcp/find-script-references.md
What find_script_references does on Godot
AI agents call find_script_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 |
|---|---|---|---|
script_path | string | Yes | Script file path (e.g. 'res://scripts/player.gd') |
Parameters from the server's own tool schema.
Why find_script_references is rated Low
This tool performs a read-only query to locate references to a script within a Godot project. It retrieves and returns data about where a script is used but does not modify, delete, or execute code. No side effects or irreversible changes occur. This is a classic Read category operation—similar to search, list, or get operations.
From the tool's definition Tool name 'find_script_references' and description 'Find all scenes and nodes that use a specific script' indicate a search/query operation that retrieves information without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs find_script_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_script_references, this is the rule to start with:
find_script_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_script_references call is checked against it from then on.
Questions about find_script_references
Find all scenes and nodes 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_script_references 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_script_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_script_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_script_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_script_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_script_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