remove_navigation_region
Remove a navigation region node from the scene
This record as markdown: /tools/keeveeg-godot-mcp/remove-navigation-region.md
What remove_navigation_region does on Godot
AI agents call remove_navigation_region to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
node_path | string | Yes | Path to the navigation region node to remove |
Parameters from the server's own tool schema.
Why remove_navigation_region is rated Critical
The tool performs an irreversible deletion operation on a Godot scene node. Removing a navigation region cannot be undone without manual re-creation, making this a Destructive action rather than a simple Write operation. In the context of an AI agent with scene manipulation capabilities, accidental or malicious removal of navigation nodes could break game functionality and require manual repair.
From the tool's definition Tool name 'remove_navigation_region' and description 'Remove a navigation region node from the scene' indicate irreversible deletion of a scene node.
Attacks that exploit this kind of access
The rule that runs remove_navigation_region safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_navigation_region, this is the rule to start with:
remove_navigation_region 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 Godot, apply this rule, and every remove_navigation_region call is checked against it from then on.
Questions about remove_navigation_region
Remove a navigation region node from the scene. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_navigation_region accepts 1 parameter: node_path. Required: node_path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for remove_navigation_region: 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. Nothing to install.
remove_navigation_region 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 remove_navigation_region 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 remove_navigation_region. 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.
remove_navigation_region is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
Across the catalogue