node_delete
Delete a node (undoable). DESTRUCTIVE — gated by confirmation. Refuses to delete the scene root.
This record as markdown: /tools/breakpoint-mcp/node-delete.md
What node_delete does on Breakpoint
AI agents call node_delete to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Node path relative to the scene root |
confirm | boolean | — | Skip the confirmation prompt (auto-approve) |
Parameters from the server's own tool schema.
Why node_delete is rated Critical
This tool irreversibly removes a node from a Godot scene. Although the description says '(undoable)', the label 'DESTRUCTIVE' and the delete operation itself indicate the action cannot be reversed within normal workflow. The presence of confirmation gates and refusal to delete root nodes shows awareness of the severity, but the core operation is still destructive.
From the tool's definition Tool name is 'node_delete' and description explicitly states 'Delete a node (undoable). DESTRUCTIVE'. The description confirms destructive intent and notes it is 'gated by confirmation' and 'Refuses to delete the scene root', indicating protective guardrails.
Risk signalsAccepts file system path (path) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs node_delete 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_delete, this is the rule to start with:
node_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every node_delete call is checked against it from then on.
Questions about node_delete
Delete a node (undoable). DESTRUCTIVE — gated by confirmation. Refuses to delete the scene root. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
node_delete accepts 2 parameters: path, confirm. 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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the node_delete 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_delete. 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_delete 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.
Across the catalogue