node_set_owner
Set a node's owner (undoable). Owner must be an ancestor; "." or omitted sets the scene root. Ownership determines which scene a node is saved into.
This record as markdown: /tools/breakpoint-mcp/node-set-owner.md
What node_set_owner does on Breakpoint
AI agents use node_set_owner 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 |
owner_path | string | — | Ancestor to own the node; "." or omitted for the scene root |
Parameters from the server's own tool schema.
Why node_set_owner is rated Medium
This tool modifies node ownership metadata, which affects scene organization and persistence. While the operation is undoable (reversible), it is a Write operation that changes data structure. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Set a node's owner (undoable)' and 'Ownership determines which scene a node is saved into.' The 'undoable' qualifier and context of modifying ownership metadata (determining which scene a node is saved into) indicates a reversible…
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs node_set_owner 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_set_owner, this is the rule to start with:
node_set_owner 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_set_owner call is checked against it from then on.
Questions about node_set_owner
Set a node's owner (undoable). Owner must be an ancestor; "." or omitted sets the scene root. Ownership determines which scene a node is saved into. 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_set_owner accepts 2 parameters: path, owner_path. Required: 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_set_owner: 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_set_owner 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_set_owner 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_set_owner. 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_set_owner 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