This record as markdown: /tools/breakpoint-mcp/node-rename.md
What node_rename does on Breakpoint
AI agents use node_rename 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_name | string | Yes | New node name |
Parameters from the server's own tool schema.
Why node_rename is rated Medium
The tool modifies data (node names) but the operation is explicitly undoable, making it reversible rather than destructive. This qualifies as Write category. Severity is medium because renaming nodes could break references or dependencies in a breakpoint/animation system if done carelessly, but the operation can be undone.
From the tool's definition Tool name 'node_rename' and description states 'Rename a node (undoable)' — a reversible modification operation.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs node_rename 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_rename, this is the rule to start with:
node_rename 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_rename call is checked against it from then on.
Questions about node_rename
Rename a node (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_rename accepts 2 parameters: path, new_name. Required: path, new_name. 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_rename: 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_rename 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_rename 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_rename. 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_rename 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