This record as markdown: /tools/keeveeg-godot-mcp/find-navigation-path.md
What find_navigation_path does on Godot
AI agents call find_navigation_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 |
|---|---|---|---|
end | array | Yes | End position [x, y] or [x, y, z] |
start | array | Yes | Start position [x, y] or [x, y, z] |
dimension | string | — | Dimension type (auto-detected if omitted) |
Parameters from the server's own tool schema.
Why find_navigation_path is rated Low
This tool retrieves pathfinding information between two points in a Godot game environment. It performs a computation and returns results without creating, modifying, deleting, or executing arbitrary code. The operation is read-only with no side effects on game assets or data structures.
From the tool's definition Tool name 'find_navigation_path' and description 'Find a navigation path between two points' indicate a query/retrieval operation that computes pathfinding without modifying game state or data.
Attacks that exploit this kind of access
The rule that runs find_navigation_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 find_navigation_path, this is the rule to start with:
find_navigation_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 find_navigation_path call is checked against it from then on.
Questions about find_navigation_path
Find a navigation path between two points. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
find_navigation_path accepts 3 parameters: end, start, dimension. Required: end, start. 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 find_navigation_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.
find_navigation_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 find_navigation_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 find_navigation_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.
find_navigation_path is provided by the Godot MCP server (@keeveeg/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