read_occluder

List OccluderInstance3D and OcclusionPolygon2D nodes.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/read-occluder.md

WHAT IT DOES

What read_occluder does on Godot

AI agents call read_occluder 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
`scene_path`	object	—

Parameters from the server's own tool schema.

RISK

Why read_occluder is rated Low

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

RECOMMENDED RULE

The rule that runs read_occluder 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_occluder, this is the rule to start with:

read_occluder Allowed

read_occluder is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "read_occluder": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every read_occluder call is checked against it from then on.

FAQ

Questions about read_occluder

What does the read_occluder tool do? +

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.

What parameters does read_occluder accept? +

read_occluder accepts 1 parameter: scene_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_occluder? +

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.

What risk level is read_occluder? +

read_occluder is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit read_occluder? +

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.

How do I block read_occluder completely? +

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.

What MCP server provides read_occluder? +

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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →