unity_navmesh_clear
Clear all baked NavMeshes from the scene.
This record as markdown: /tools/anklebreaker-studio-unity-mcp-server/unity-navmesh-clear.md
What unity_navmesh_clear does on Unity MCP Server
AI agents call unity_navmesh_clear to permanently remove resources in Unity MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unity_navmesh_clear is rated Critical
This operation destroys pre-existing scene data (baked NavMeshes) in an irreversible manner. While re-baking is possible, the original baked state is permanently lost. The tool fits the Destructive category as it performs an action that cannot be undone without manual intervention. The high severity reflects the potential disruption to game navigation logic if invoked unintentionally during active development.
From the tool's definition "Clear all baked NavMeshes from the scene" – the tool irreversibly removes navigation mesh data that has been pre-computed and baked into the scene, which cannot be automatically recovered without re-baking.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs unity_navmesh_clear safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Unity MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unity_navmesh_clear, this is the rule to start with:
unity_navmesh_clear is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Unity MCP Server, apply this rule, and every unity_navmesh_clear call is checked against it from then on.
Questions about unity_navmesh_clear
Clear all baked NavMeshes from the scene. It is categorised as a Destructive tool in the Unity MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_navmesh_clear: 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 Unity MCP Server. Nothing to install.
unity_navmesh_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unity_navmesh_clear 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 unity_navmesh_clear. 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.
unity_navmesh_clear is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Unity MCP Server, and thousands of servers like it.
Across the catalogue