This record as markdown: /tools/yanhuifair-godot-mcp/create-nav-mesh.md
What create_nav_mesh does on Godot
AI agents use create_nav_mesh 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Output path for NavigationMesh .tres |
cell_size | object | — | Voxel cell size |
cell_height | object | — | Voxel cell height |
agent_height | object | — | Agent height |
agent_radius | object | — | Agent radius |
Parameters from the server's own tool schema.
Why create_nav_mesh is rated Medium
This tool creates a new NavigationMesh resource file, which is a reversible write operation. It does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because creating or modifying game assets could impact game behavior or introduce unintended navigation logic, but the change can be undone by deleting the file.
From the tool's definition Tool name 'create_nav_mesh' and description 'Create NavigationMesh .tres' indicate creation of a new resource file (.tres is Godot's text resource format).
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_nav_mesh 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 create_nav_mesh, this is the rule to start with:
create_nav_mesh 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 create_nav_mesh call is checked against it from then on.
Questions about create_nav_mesh
Create NavigationMesh .tres. 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.
create_nav_mesh accepts 5 parameters: path, cell_size, cell_height, agent_height, agent_radius. Required: 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 create_nav_mesh: 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.
create_nav_mesh 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 create_nav_mesh 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 create_nav_mesh. 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.
create_nav_mesh 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue