This record as markdown: /tools/chanceflow-godot-mcp/navigation-add-agent.md
What navigation_add_agent does on Godot
AI agents use navigation_add_agent to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
Why navigation_add_agent is rated Medium
The 'add' pattern aligns with reversible Write operations (creating game entities). In a game engine context, adding an agent creates a new scene node/component that can be modified or deleted later. This is less severe than Execute (which would run arbitrary code) or Destructive (which would irreversibly delete). Confidence is moderate due to the empty description and reliance on naming convention alone.
From the tool's definition Tool name 'navigation_add_agent' suggests adding/creating a navigation agent entity in Godot. The 'add' verb indicates creation of a new game object or component. Description is empty, limiting precision.
Attacks that exploit this kind of access
The rule that runs navigation_add_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 navigation_add_agent, this is the rule to start with:
navigation_add_agent stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 navigation_add_agent call is checked against it from then on.
Questions about navigation_add_agent
navigation_add_agent is a write tool on the Godot MCP server. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP server in PolicyLayer and add a rule for navigation_add_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.
navigation_add_agent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the navigation_add_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.
Set action: deny in the PolicyLayer policy for navigation_add_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.
navigation_add_agent is provided by the Godot MCP server (chanceflow/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