add_scene_instance
Add an instance of a scene as a child of a node in the current scene
This record as markdown: /tools/keeveeg-godot-mcp/add-scene-instance.md
What add_scene_instance does on Godot
AI agents use add_scene_instance to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene_path | string | Yes | Path to the scene to instantiate |
parent_path | string | — | Parent node path, defaults to scene root |
Parameters from the server's own tool schema.
Why add_scene_instance is rated Medium
This tool creates a new scene instance within the Godot project, modifying the scene structure reversibly. While it changes project state, the action is not destructive (can be undone/deleted) and does not execute arbitrary code or affect financial systems. It falls under Write category as a creative/additive operation.
From the tool's definition Tool name 'add_scene_instance' and description 'Add an instance of a scene as a child of a node in the current scene' indicate creation/modification of scene hierarchy.
Attacks that exploit this kind of access
The rule that runs add_scene_instance 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 add_scene_instance, this is the rule to start with:
add_scene_instance stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_scene_instance call is checked against it from then on.
Questions about add_scene_instance
Add an instance of a scene as a child of a node in the current scene. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_scene_instance accepts 2 parameters: scene_path, parent_path. Required: scene_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 add_scene_instance: 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.
add_scene_instance is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_scene_instance 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 add_scene_instance. 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.
add_scene_instance 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