editor_bake_navigation · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_bake_navigation does on Godot

AI agents invoke editor_bake_navigation 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.

WHY IT NEEDS A POLICY

Why editor_bake_navigation needs a policy

Baking navigation meshes is a computational operation that triggers an external process (the Godot editor's navigation mesh generation) and modifies scene assets by generating/overwriting navigation mesh data. It spans Write and Execute; Execute is more appropriate since it triggers an editor operation with side effects dependent on scene state.

From the tool's definition Bake navigation meshes for all NavigationRegion nodes in current scene

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_bake_navigation Rate-limited

editor_bake_navigation 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_bake_navigation": {
      "limits": [
        {
          "counter": "editor_bake_navigation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about editor_bake_navigation

What does the editor_bake_navigation tool do? +

Bake navigation meshes for all NavigationRegion nodes in current scene. 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.

How do I enforce a policy on editor_bake_navigation? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_bake_navigation: 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.

What risk level is editor_bake_navigation? +

editor_bake_navigation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit editor_bake_navigation? +

Yes. Add a rate_limit block to the editor_bake_navigation 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.

How do I block editor_bake_navigation completely? +

Set action: deny in the PolicyLayer policy for editor_bake_navigation. 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.

What MCP server provides editor_bake_navigation? +

editor_bake_navigation is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

editor_bake_navigation is one line of Godot's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →