editor_bake_lightmaps · Godot MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why editor_bake_lightmaps needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_bake_lightmaps Rate-limited

editor_bake_lightmaps 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_lightmaps": {
      "limits": [
        {
          "counter": "editor_bake_lightmaps_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_lightmaps

What does the editor_bake_lightmaps tool do? +

Trigger lightmap baking. 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_lightmaps? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_bake_lightmaps: 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_lightmaps? +

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

Can I rate-limit editor_bake_lightmaps? +

Yes. Add a rate_limit block to the editor_bake_lightmaps 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_lightmaps completely? +

Set action: deny in the PolicyLayer policy for editor_bake_lightmaps. 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_lightmaps? +

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