list_nav_regions

List NavigationRegion 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/list-nav-regions.md

WHAT IT DOES

What list_nav_regions does on Godot

AI agents call list_nav_regions 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	—	Filter to a specific scene

Parameters from the server's own tool schema.

RISK

Why list_nav_regions is rated Low

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

RECOMMENDED RULE

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

list_nav_regions Allowed

list_nav_regions 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": {
    "list_nav_regions": {}
  }
}

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 list_nav_regions call is checked against it from then on.

FAQ

Questions about list_nav_regions

What does the list_nav_regions tool do? +

List NavigationRegion nodes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

What parameters does list_nav_regions accept? +

list_nav_regions 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 list_nav_regions? +

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.

What risk level is list_nav_regions? +

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

Can I rate-limit list_nav_regions? +

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.

How do I block list_nav_regions completely? +

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.

What MCP server provides list_nav_regions? +

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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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