This record as markdown: /tools/yanhuifair-godot-mcp/read-path.md
What read_path does on Godot
AI agents call read_path 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 |
|---|---|---|---|
name | object | — | Path2D/Path3D node name |
scene_path | string | Yes | Path to .tscn scene |
Parameters from the server's own tool schema.
Why read_path is rated Low
This tool retrieves or queries data about a Path node and its associated curve in Godot, which is a read-only operation with no side effects. The verb 'read' and the absence of language indicating state change or resource consumption confirms Read classification. The low severity reflects that accessing node configuration data poses minimal risk even if retrieved unexpectedly by an AI agent.
From the tool's definition Tool name 'read_path' with description 'Read Path node with curve' indicates retrieval of Path node configuration and curve data without modification.
Attacks that exploit this kind of access
The rule that runs read_path 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_path, this is the rule to start with:
read_path 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_path call is checked against it from then on.
Questions about read_path
Read Path node with curve. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
read_path accepts 2 parameters: name, scene_path. Required: 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_path: 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_path 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_path 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_path. 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_path 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