bake_navigation_mesh
Bake the navigation mesh for a NavigationRegion
This record as markdown: /tools/keeveeg-godot-mcp/bake-navigation-mesh.md
What bake_navigation_mesh does on Godot
AI agents invoke bake_navigation_mesh to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | NavigationRegion node path |
properties | object | — | Bake configuration (cell_size, cell_height, agent_radius, etc.) |
Parameters from the server's own tool schema.
Why bake_navigation_mesh is rated High
Baking a navigation mesh is a computational operation that processes/generates data (the nav mesh) for a scene node. It triggers an external engine operation with side effects on the scene state, fitting Execute. It's not purely destructive (prior mesh can be rebaked) but it does modify the NavigationRegion's mesh data.
From the tool's definition Bake the navigation mesh for a NavigationRegion
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs bake_navigation_mesh 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 bake_navigation_mesh, this is the rule to start with:
bake_navigation_mesh stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every bake_navigation_mesh call is checked against it from then on.
Questions about bake_navigation_mesh
Bake the navigation mesh for a NavigationRegion. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
bake_navigation_mesh accepts 2 parameters: path, properties. Required: 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 bake_navigation_mesh: 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.
bake_navigation_mesh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bake_navigation_mesh 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 bake_navigation_mesh. 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.
bake_navigation_mesh 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