AI agents call list_nav_regions 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 | — | Filter to a specific scene |
Parameters from the server's own tool schema.
The tool retrieves and lists existing NavigationRegion nodes from the Godot scene, similar to a get or fetch operation. There is no modification, execution, deletion, or financial impact. The blast radius of misuse is minimal—an agent could only learn about navigation regions in the scene. This is a standard Read operation.
From the tool's definition Tool name 'list_nav_regions' and description 'List NavigationRegion nodes' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List NavigationRegion nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
list_nav_regions 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 list_nav_regions: 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.
list_nav_regions 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 list_nav_regions 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 list_nav_regions. 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.
list_nav_regions 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.
list_nav_regions 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 →