node_instantiate_scene
Instance an external PackedScene (res:// path) as an editable child of a parent node (undoable). Returns the new node's path.
This record as markdown: /tools/breakpoint-mcp/node-instantiate-scene.md
What node_instantiate_scene does on Breakpoint
AI agents use node_instantiate_scene to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Node name (defaults to the instanced scene's root name) |
scene_path | string | Yes | Scene to instance, e.g. res://actors/enemy.tscn |
parent_path | string | Yes | Parent node path relative to the scene root; "." for the root |
Parameters from the server's own tool schema.
Why node_instantiate_scene is rated Medium
This tool creates a new node by instantiating a scene, which is a reversible data modification operation (marked 'undoable'). It does not execute arbitrary code, delete data, or perform financial operations.
From the tool's definition Tool description explicitly states 'Instance an external PackedScene as an editable child of a parent node (undoable)'. The verb 'instance' combined with 'editable child' indicates creation of a new node/object in the scene hierarchy.
Attacks that exploit this kind of access
The rule that runs node_instantiate_scene safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_instantiate_scene, this is the rule to start with:
node_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 Breakpoint, apply this rule, and every node_instantiate_scene call is checked against it from then on.
Questions about node_instantiate_scene
Instance an external PackedScene (res:// path) as an editable child of a parent node (undoable). Returns the new node's path. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
node_instantiate_scene accepts 3 parameters: name, scene_path, parent_path. Required: scene_path, parent_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for node_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 Breakpoint. Nothing to install.
node_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 node_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 node_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.
node_instantiate_scene is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue