Configure LightmapGI node in a scene for baked lighting, optionally trigger lightmap baking
AI agents invoke setup_lightmapper to trigger actions in Godot MCP Unified. 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.
The tool configures a LightmapGI node (Write) but also optionally triggers lightmap baking, which executes a rendering/computation process that generates and writes baked lighting data to assets. The most severe applicable category is Execute due to the triggered baking operation.
From the tool's definition 'optionally trigger lightmap baking' — baking is a computational process that runs an operation (lightmap generation) and modifies scene assets
Attacks that exploit this kind of access
Configure LightmapGI node in a scene for baked lighting, optionally trigger lightmap baking. It is categorised as a Execute tool in the Godot MCP Unified MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for setup_lightmapper: 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 Unified. Nothing to install.
setup_lightmapper 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 setup_lightmapper 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 setup_lightmapper. 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.
setup_lightmapper is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →