This record as markdown: /tools/yanhuifair-godot-mcp/set-light-param.md
What set_light_param does on Godot
AI agents use set_light_param 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 |
|---|---|---|---|
param | string | Yes | Light parameter (e.g. "energy", "color", "shadow_enabled") |
value | string | Yes | New value |
light_name | string | Yes | Name of the light node |
scene_path | string | Yes | Path to .tscn scene file |
Parameters from the server's own tool schema.
Why set_light_param is rated Medium
This tool modifies engine configuration state (light parameters) but does not execute arbitrary code, delete data, or produce financial effects. The change is reversible through subsequent set operations. Categorized as Write rather than Execute because it targets a specific, bounded parameter rather than arbitrary code execution.
From the tool's definition Tool name 'set_light_param' and description 'Set light parameter' indicate modification of light properties in the Godot Engine. This creates or modifies engine state (light parameters) reversibly.
Attacks that exploit this kind of access
The rule that runs set_light_param 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 set_light_param, this is the rule to start with:
set_light_param 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 set_light_param call is checked against it from then on.
Questions about set_light_param
Set light parameter. 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.
set_light_param accepts 4 parameters: param, value, light_name, scene_path. Required: param, value, light_name, scene_path. 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 set_light_param: 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.
set_light_param 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 set_light_param 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 set_light_param. 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.
set_light_param 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue