This record as markdown: /tools/yanhuifair-godot-mcp/read-raycast.md
What read_raycast does on Godot
AI agents call read_raycast 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 |
|---|---|---|---|
ray_type | object | — | Filter: RayCast2D, RayCast3D, ShapeCast2D, ShapeCast3D |
scene_path | object | — | Filter to scene |
Parameters from the server's own tool schema.
Why read_raycast is rated Low
This tool retrieves information about RayCast and ShapeCast nodes in the Godot scene tree. It performs a read-only operation (listing/querying) with no capability to modify, execute, or delete data. The 'read' prefix and 'List' verb confirm the informational nature of this operation.
From the tool's definition Tool name 'read_raycast' and description 'List RayCast/ShapeCast nodes' indicates querying/listing existing nodes without modification or side effects.
Attacks that exploit this kind of access
The rule that runs read_raycast 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_raycast, this is the rule to start with:
read_raycast 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_raycast call is checked against it from then on.
Questions about read_raycast
List RayCast/ShapeCast nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_raycast accepts 2 parameters: ray_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_raycast: 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_raycast 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_raycast 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_raycast. 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_raycast 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