Inspect the workspace file tree without reading file contents. Use this first to orient in an unfamiliar area, then narrow with code.find_symbol, code.list_endpoints, or code.search_text before reading files.
AI agents call code.inspect_tree to retrieve information from Navigation Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata (file tree/directory listing) about a codebase without accessing file contents or modifying anything. It has no side effects and serves purely as a query/inspection mechanism. The lack of content reading, modification capability, or external operation execution places it squarely in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Inspect the workspace file tree without reading file contents' and is positioned as an orientation/navigation tool alongside symbol searching and call tracing on a 'code navigation' server.
Attacks that exploit this kind of access
Inspect the workspace file tree without reading file contents. Use this first to orient in an unfamiliar area, then narrow with code.find_symbol, code.list_endpoints, or code.search_text before reading files. It is categorised as a Read tool in the Navigation Agent MCP Server, which means it retrieves data without modifying state.
Register the Navigation Agent MCP server in PolicyLayer and add a rule for code.inspect_tree: 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 Navigation Agent. Nothing to install.
code.inspect_tree is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the code.inspect_tree 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 code.inspect_tree. 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.
code.inspect_tree is provided by the Navigation Agent MCP server (j0k3r-dev-rgl/navigation-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →