editor_bake_lightmaps

What editor_bake_lightmaps does on Godot

AI agents invoke editor_bake_lightmaps 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 editor_bake_lightmaps is rated High

Lightmap baking is a compute-intensive background process that modifies the project's lighting data and cached assets. While not destructive in the sense of data deletion, it is an Execute-category operation because: (1) it runs an external rendering/compilation process, (2) the effects persist in generated artifacts, (3) an AI agent could waste resources or corrupt lighting by triggering it with invalid parameters,…

From the tool's definition Trigger lightmap baking — the verb 'trigger' indicates this tool initiates an external operation (lightmap rendering/computation) whose effects depend on project configuration and cannot be simply undone by reversing parameters.

The rule that runs editor_bake_lightmaps 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 editor_bake_lightmaps, this is the rule to start with:

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

Questions about editor_bake_lightmaps