directory_tree
Get a recursive tree view of files and directories as a JSON structure. Each entry includes 'name', 'type' (file/directory), and 'children' for directories. Files have no children array, while directories always have a children array (which may be empty). The output is formatted with 2-space inde...
This record as markdown: /tools/filesystem/directory-tree.md
What directory_tree does on Filesystem
AI agents call directory_tree to retrieve information from Filesystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | |
excludePatterns | array | — |
Parameters from the server's own tool schema.
Why directory_tree is rated Low
This tool only queries and returns file/directory structure information without any capability to create, modify, delete, or execute operations. It is purely a read operation with minimal side effects, appropriate for directory navigation and inspection.
From the tool's definition Tool retrieves a recursive tree view of files and directories as JSON structure with no modification capability. Description explicitly states it 'Get[s]' data and works 'within allowed directories', indicating query-only access.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs directory_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For directory_tree, this is the rule to start with:
directory_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Filesystem, apply this rule, and every directory_tree call is checked against it from then on.
Questions about directory_tree
Get a recursive tree view of files and directories as a JSON structure. Each entry includes 'name', 'type' (file/directory), and 'children' for directories. Files have no children array, while directories always have a children array (which may be empty). The output is formatted with 2-space indentation for readability. Only works within allowed directories. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
directory_tree accepts 2 parameters: path, excludePatterns. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem MCP server in PolicyLayer and add a rule for directory_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 Filesystem. Nothing to install.
directory_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 directory_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 directory_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.
directory_tree is provided by the Filesystem MCP server (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue