Create a Light2D or Light3D node for scene lighting
AI agents use create_light to create or update resources in Godot MCP Unified — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Unified environment.
Creating a node is a Write operation: it modifies scene state by adding a new node object, but the action is reversible (the node can be deleted). This is not Execute (no code/script execution), not Destructive (reversible), not Read (creates rather than retrieves), and not Financial. Severity is medium because misuse could corrupt a scene or cause unintended visual/performance changes, but these can be undone.
From the tool's definition Tool creates a Light2D or Light3D node in the scene—this is a reversible creation action that modifies the scene structure. The description explicitly states it creates a lighting node.
Attacks that exploit this kind of access
Create a Light2D or Light3D node for scene lighting. It is categorised as a Write tool in the Godot MCP Unified MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for create_light: 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.
create_light 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 create_light 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 create_light. 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.
create_light 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 →