AI agents call read_occluder to retrieve information from Godot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
scene_path | object | — |
Parameters from the server's own tool schema.
This tool retrieves and lists occluder nodes from a Godot scene. It performs no mutations, does not execute code, and does not delete or create data. It is a straightforward read operation to query scene structure, making it a Read category tool with low severity since listing scene nodes poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'read_occluder' and description states 'List OccluderInstance3D and OcclusionPolygon2D nodes' — a pure listing/query operation with no modification or side effects.
Attacks that exploit this kind of access
List OccluderInstance3D and OcclusionPolygon2D nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_occluder accepts 1 parameter: 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_occluder: 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_occluder 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_occluder 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_occluder. 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_occluder 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.
read_occluder is one line of Godot's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →