# directory_tree

Get a recursive tree view of files and directories as a JSON structure.

Agent View of the PolicyLayer registry record for `directory_tree`. HTML page: https://policylayer.com/tools/a-niranjan-mcp-filesystem/directory-tree

## Facts

- Tool: `directory_tree`
- Server: MCP Filesystem Server (`a-niranjan/mcp-filesystem`) — https://policylayer.com/tools/a-niranjan-mcp-filesystem.md
- Homepage: https://github.com/A-Niranjan/mcp-filesystem
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "directory_tree",
    "arguments": {}
  }
}
```

## Why directory_tree is rated Low

This tool retrieves and queries filesystem metadata (directory structure and file listing) with no side effects. It does not create, modify, delete, or execute anything—it only returns information about existing directory contents in JSON format. The 'Get' verb and lack of any mutation capability clearly categorize this as a Read operation with low severity.

From the tool's own definition: "Tool name 'directory_tree' and description 'Get a recursive tree view of files and directories as a JSON structure' indicate a read-only operation that retrieves directory information without modification."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches MCP Filesystem Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "directory_tree": {}
  }
}
```

## Other tools on MCP Filesystem Server (16)

- `bash_command` — Execute — https://policylayer.com/tools/a-niranjan-mcp-filesystem/bash-command.md
- `bash_execute` — Execute — https://policylayer.com/tools/a-niranjan-mcp-filesystem/bash-execute.md
- `bash_pipe` — Execute — https://policylayer.com/tools/a-niranjan-mcp-filesystem/bash-pipe.md
- `curl_request` — Execute — https://policylayer.com/tools/a-niranjan-mcp-filesystem/curl-request.md
- `execute_command` — Execute — https://policylayer.com/tools/a-niranjan-mcp-filesystem/execute-command.md
- `get_file_info` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/get-file-info.md
- `get_metrics` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/get-metrics.md
- `list_allowed_directories` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/list-allowed-directories.md
- `list_directory` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/list-directory.md
- `read_file` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/read-file.md
- `read_multiple_files` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/read-multiple-files.md
- `search_files` — Read — https://policylayer.com/tools/a-niranjan-mcp-filesystem/search-files.md
- `create_directory` — Write — https://policylayer.com/tools/a-niranjan-mcp-filesystem/create-directory.md
- `edit_file` — Write — https://policylayer.com/tools/a-niranjan-mcp-filesystem/edit-file.md
- `move_file` — Write — https://policylayer.com/tools/a-niranjan-mcp-filesystem/move-file.md
- `write_file` — Write — https://policylayer.com/tools/a-niranjan-mcp-filesystem/write-file.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a-niranjan-mcp-filesystem · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a-niranjan-mcp-filesystem