bake_navigation_mesh · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What bake_navigation_mesh does on Godot MCP Server

AI agents invoke bake_navigation_mesh to trigger actions in Godot MCP Server. 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 bake_navigation_mesh needs a policy

Baking a navigation mesh is an execution operation that runs a computation (geometry processing) and modifies editor state by generating or overwriting the navigation mesh data. It is not a simple read, nor is it a destructive delete, but it does trigger an external operation in the Godot editor with side effects on the scene's navigation data.

From the tool's definition 'Bake the navigation mesh for a NavigationRegion3D node' — baking triggers a computational operation that processes geometry and generates/overwrites navigation data within the Godot editor.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bake_navigation_mesh Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bake_navigation_mesh": {
      "limits": [
        {
          "counter": "bake_navigation_mesh_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about bake_navigation_mesh

What does the bake_navigation_mesh tool do? +

Bake the navigation mesh for a NavigationRegion3D node. It is categorised as a Execute tool in the Godot MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bake_navigation_mesh? +

Register the Godot MCP Server 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 MCP Server. Nothing to install.

What risk level is bake_navigation_mesh? +

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

Can I rate-limit bake_navigation_mesh? +

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.

How do I block bake_navigation_mesh completely? +

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.

What MCP server provides bake_navigation_mesh? +

bake_navigation_mesh is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.