node_add
Instance a node of the given class under a parent path (undoable). Returns the new node's path.
This record as markdown: /tools/breakpoint-mcp/node-add.md
What node_add does on Breakpoint
AI agents use node_add 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 class name) |
type | string | Yes | Node class to instance, e.g. Sprite2D, AudioStreamPlayer3D |
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_add is rated Medium
This tool creates a new node within a parent hierarchy, which is a write operation that modifies the scene structure. The reversibility (undoable) and the creation (not deletion) context classify it as Write rather than Destructive or Execute.
From the tool's definition Tool description states "Instance a node" and "Returns the new node's path". The term "instance" indicates creation of a new object. The note "(undoable)" confirms the action is reversible, distinguishing it from destructive operations.
Attacks that exploit this kind of access
The rule that runs node_add 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_add, this is the rule to start with:
node_add 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_add call is checked against it from then on.
Questions about node_add
Instance a node of the given class under a parent path (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_add accepts 3 parameters: name, type, parent_path. Required: type, 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_add: 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_add 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_add 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_add. 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_add 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