read_nav_agent

Read NavigationAgent properties across scenes.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/read-nav-agent.md

WHAT IT DOES

What read_nav_agent does on Godot

AI agents call read_nav_agent 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
`agent_name`	object	—	Specific NavigationAgent node name
`scene_path`	string	Yes	Path to .tscn scene

Parameters from the server's own tool schema.

RISK

Why read_nav_agent is rated Low

Tool retrieves NavigationAgent properties with no ability to modify, execute, or delete data.

From the tool's definition Read NavigationAgent properties across scenes

Attacks that exploit this kind of access

RECOMMENDED RULE

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

read_nav_agent Allowed

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

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

FAQ

Questions about read_nav_agent

What does the read_nav_agent tool do? +

Read NavigationAgent properties across scenes. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

What parameters does read_nav_agent accept? +

read_nav_agent accepts 2 parameters: agent_name, scene_path. Required: scene_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_nav_agent? +

Register the Godot MCP server in PolicyLayer and add a rule for read_nav_agent: 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 read_nav_agent? +

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

Can I rate-limit read_nav_agent? +

Yes. Add a rate_limit block to the read_nav_agent 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 read_nav_agent completely? +

Set action: deny in the PolicyLayer policy for read_nav_agent. 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 read_nav_agent? +

read_nav_agent 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 386 Godot tools →

Across the catalogue

binary_read on 010 Editor →comfy_agent_compute on Comfy → The MCP Attack Database →

Guides

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