editor_instantiate_scene
Instantiate a PackedScene into the current scene.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-instantiate-scene.md
What editor_instantiate_scene does on Godot
AI agents use editor_instantiate_scene 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 |
|---|---|---|---|
name | object | — | |
scene | string | Yes | PackedScene path to instantiate |
parent | object | — |
Parameters from the server's own tool schema.
Why editor_instantiate_scene is rated Medium
This tool creates a new instance of a scene and adds it to the current scene, which is a reversible write operation (the instantiated node can be removed). It modifies the scene's node tree but does not execute arbitrary code, delete data, or involve financial transactions.
From the tool's definition Instantiate a PackedScene into the current scene
Attacks that exploit this kind of access
The rule that runs editor_instantiate_scene 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 editor_instantiate_scene, this is the rule to start with:
editor_instantiate_scene 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 editor_instantiate_scene call is checked against it from then on.
Questions about editor_instantiate_scene
Instantiate a PackedScene into 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.
editor_instantiate_scene accepts 3 parameters: name, scene, parent. Required: scene. 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 editor_instantiate_scene: 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.
editor_instantiate_scene 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 editor_instantiate_scene 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 editor_instantiate_scene. 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.
editor_instantiate_scene is provided by the Godot MCP server (@yanhuifair/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