setup_lighting
Add a light node (DirectionalLight3D, OmniLight3D, SpotLight3D)
This record as markdown: /tools/keeveeg-godot-mcp/setup-lighting.md
What setup_lighting does on Godot
AI agents use setup_lighting to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Light type |
parent | string | Yes | Parent node path. Use '' (empty string) to add at scene root, or a node name/path (e.g. 'Player' or 'Player/Sprites') to add as a child of that node. |
properties | object | — | Light properties (color, energy, position, shadow_enabled, etc.) |
Parameters from the server's own tool schema.
Why setup_lighting is rated Medium
This tool creates new nodes in the Godot scene hierarchy, which is a reversible modification operation. It falls under Write rather than Execute because it's a high-level scene composition action rather than arbitrary code execution. The severity is medium because modifying scene structure could affect rendering and gameplay, but changes are easily undone by removing the node.
From the tool's definition Tool adds a light node to the Godot scene - this creates and modifies scene graph state. The description explicitly states 'Add a light node' with specific types (DirectionalLight3D, OmniLight3D, SpotLight3D).
Attacks that exploit this kind of access
The rule that runs setup_lighting 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 setup_lighting, this is the rule to start with:
setup_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every setup_lighting call is checked against it from then on.
Questions about setup_lighting
Add a light node (DirectionalLight3D, OmniLight3D, SpotLight3D). It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
setup_lighting accepts 3 parameters: type, parent, properties. Required: type, parent. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for setup_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. Nothing to install.
setup_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 setup_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 setup_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.
setup_lighting is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue