AI agents use lighting to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
Creating light and environment nodes modifies the Godot project state by adding objects to the scene hierarchy. This is reversible (nodes can be deleted) and does not execute arbitrary code or permanently destroy data. It is categorized as Write rather than Read because creation is the primary capability.
From the tool's definition Tool description states 'Create and list basic Godot light and environment nodes'. The 'create' verb indicates the tool modifies the scene graph by adding new nodes, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access lighting gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for lighting:
{
"version": "1",
"default": "deny",
"tools": {
"lighting": {
"limits": [
{
"counter": "lighting_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lighting stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create and list basic Godot light and environment nodes. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for lighting: 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 Devtool. Nothing to install.
lighting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lighting 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 lighting. 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.
lighting is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.