This record as markdown: /tools/breakpoint-mcp/node-reparent.md
What node_reparent does on Breakpoint
AI agents use node_reparent 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 |
new_parent_path | string | Yes | New parent path; "." for the root |
keep_global_transform | boolean | — | Preserve global transform (default true) |
Parameters from the server's own tool schema.
Why node_reparent is rated Medium
The tool creates a modification to data (node hierarchy) that can be reversed/undone. This is a structural modification without permanent loss, and the tool set suggests a 3D/animation editor context where scene manipulation is expected. Severity is medium because misuse could disrupt a scene's organization or cause cascading effects if nodes are moved inappropriately, but the undoable nature mitigates damage.
From the tool's definition Tool description states 'Move a node under a new parent (undoable)' — this modifies the scene graph structure by changing parent-child relationships.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_reparent 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_reparent, this is the rule to start with:
node_reparent 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_reparent call is checked against it from then on.
Questions about node_reparent
Move a node under a new parent (undoable). 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_reparent accepts 3 parameters: path, new_parent_path, keep_global_transform. Required: path, new_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_reparent: 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_reparent 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_reparent 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_reparent. 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_reparent 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