node_change_type
Replace a node with a new node of a different class, carrying over compatible properties, children, and groups (undoable). Refuses the scene root.
This record as markdown: /tools/godot-breakpoint-mcp/node-change-type.md
What node_change_type does on Godot Breakpoint
AI agents use node_change_type to create or update resources in Godot Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Breakpoint environment.
Why node_change_type is rated Medium
This tool modifies the scene tree by replacing a node with one of a different type. It is explicitly stated to be undoable, so it is reversible, placing it in the Write category rather than Destructive. However, the blast radius is high because replacing a node's type can break scripts, signals, and scene logic if done incorrectly.
From the tool's definition Replace a node with a new node of a different class, carrying over compatible properties, children, and groups (undoable). Refuses the scene root.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs node_change_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_change_type, this is the rule to start with:
node_change_type 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 Godot Breakpoint, apply this rule, and every node_change_type call is checked against it from then on.
Questions about node_change_type
Replace a node with a new node of a different class, carrying over compatible properties, children, and groups (undoable). Refuses the scene root. It is categorised as a Write tool in the Godot Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for node_change_type: 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 Godot Breakpoint. Nothing to install.
node_change_type 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_change_type 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_change_type. 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_change_type is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue