get_navmesh_path

Query the baked navmesh for a walkable path between two world points (NavMesh.GetSimplePath). Returns the ordered path points, or reachable:false if no route exists. Requires bake_navmesh to have run first. Read-only — useful for validating connectivity, AI patrol routes, and spawn reachability.

SERVERSbox SOURCEsbox-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sbox/get-navmesh-path.md

WHAT IT DOES

What get_navmesh_path does on Sbox

AI agents call get_navmesh_path to retrieve information from Sbox without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_navmesh_path is rated Low

This tool queries existing navigation mesh data to return path information between two points. It performs no modifications, does not execute arbitrary code, and cannot delete or move money. The explicit 'Read-only' designation and use case (validating connectivity, checking AI routes) confirm it is a safe data retrieval operation with minimal blast radius if misused.

From the tool's definition Tool description explicitly states 'Query the baked navmesh' and 'Read-only'. It retrieves path data without modifying game state or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_navmesh_path safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sbox, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_navmesh_path, this is the rule to start with:

get_navmesh_path Allowed

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sbox, apply this rule, and every get_navmesh_path call is checked against it from then on.

FAQ

Questions about get_navmesh_path

What does the get_navmesh_path tool do? +

How do I enforce a policy on get_navmesh_path? +

Register the Sbox MCP server in PolicyLayer and add a rule for get_navmesh_path: 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 Sbox. Nothing to install.

What risk level is get_navmesh_path? +

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

Can I rate-limit get_navmesh_path? +

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

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

get_navmesh_path is provided by the Sbox MCP server (sbox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sbox, and thousands of servers like it.

This server

All 207 Sbox tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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