get_scene_dependencies
Get all dependencies of a scene file (scripts, resources, sub-scenes)
This record as markdown: /tools/keeveeg-godot-mcp/get-scene-dependencies.md
What get_scene_dependencies does on Godot
AI agents call get_scene_dependencies 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 |
|---|---|---|---|
path | string | Yes | Scene file path |
Parameters from the server's own tool schema.
Why get_scene_dependencies is rated Low
This tool retrieves metadata about scene dependencies without creating, modifying, deleting, or executing anything. It is purely informational and has no side effects. The blast radius of misuse is minimal—an agent could only access information about scene structure, which is already accessible through normal project inspection.
From the tool's definition Tool name is 'get_scene_dependencies' with description 'Get all dependencies of a scene file (scripts, resources, sub-scenes)'.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs get_scene_dependencies 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 get_scene_dependencies, this is the rule to start with:
get_scene_dependencies 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 get_scene_dependencies call is checked against it from then on.
Questions about get_scene_dependencies
Get all dependencies of a scene file (scripts, resources, sub-scenes). It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
get_scene_dependencies accepts 1 parameter: path. Required: 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 get_scene_dependencies: 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.
get_scene_dependencies 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 get_scene_dependencies 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 get_scene_dependencies. 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.
get_scene_dependencies 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