node_move_child
Reorder a node among its siblings by index (undoable). Negative indices count from the end (-1 = last).
This record as markdown: /tools/breakpoint-mcp/node-move-child.md
What node_move_child does on Breakpoint
AI agents use node_move_child 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 |
|---|---|---|---|
path | string | Yes | Node path relative to the scene root |
to_index | integer | Yes | New sibling index (0-based; negative counts from the end) |
Parameters from the server's own tool schema.
Why node_move_child is rated Medium
This tool modifies the structural state of a node hierarchy (reordering children), which is a Write operation. It is not Read (has side effects), not Execute (doesn't run arbitrary code or trigger external operations), not Destructive (explicitly marked undoable, reversible), not Financial (no monetary implications).
From the tool's definition Tool description states 'Reorder a node among its siblings by index (undoable)'. The undoable nature indicates the operation is reversible, and reordering is a modification operation that changes node hierarchy state without permanent deletion.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_move_child 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_move_child, this is the rule to start with:
node_move_child 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_move_child call is checked against it from then on.
Questions about node_move_child
Reorder a node among its siblings by index (undoable). Negative indices count from the end (-1 = last). 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_move_child accepts 2 parameters: path, to_index. Required: path, to_index. 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_move_child: 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_move_child 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_move_child 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_move_child. 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_move_child 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