read_light_2d
List PointLight2D/DirectionalLight2D nodes with energy and shadow settings.
This record as markdown: /tools/yanhuifair-godot-mcp/read-light-2d.md
What read_light_2d does on Godot
AI agents call read_light_2d to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
light_type | object | — | Filter: PointLight2D, DirectionalLight2D |
scene_path | object | — | Filter to scene |
Parameters from the server's own tool schema.
Why read_light_2d is rated Low
This tool retrieves and enumerates light node configuration data from the Godot scene tree. It performs no mutations, executions, deletions, or financial operations. The read-only nature and informational purpose place it squarely in the Read category with low severity, as misuse would only expose scene metadata.
From the tool's definition Tool name includes 'read_' prefix and description states 'List PointLight2D/DirectionalLight2D nodes with energy and shadow settings' — a pure query operation that retrieves existing light node properties without modification.
Attacks that exploit this kind of access
The rule that runs read_light_2d 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 read_light_2d, this is the rule to start with:
read_light_2d is read-only, so it stays allowed. 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 read_light_2d call is checked against it from then on.
Questions about read_light_2d
List PointLight2D/DirectionalLight2D nodes with energy and shadow settings. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_light_2d accepts 2 parameters: light_type, 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 read_light_2d: 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.
read_light_2d is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the read_light_2d 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 read_light_2d. 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.
read_light_2d 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