# list_directory

List files and directories in a specified path

Agent View of the PolicyLayer registry record for `list_directory`. HTML page: https://policylayer.com/tools/deep-ai-kr-dev-mcp/list-directory

## Facts

- Tool: `list_directory`
- Server: Dev (`deep-ai-kr/dev-mcp`) — https://policylayer.com/tools/deep-ai-kr-dev-mcp.md
- Homepage: https://github.com/deep-ai-kr/dev-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `path` | string | no | Path to the directory to list (relative to root) |

Parameters from the server's own tool schema.

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

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

## Why list_directory is rated Low

This tool retrieves directory structure information without creating, modifying, deleting, or executing anything. It is a pure query operation with no side effects, fitting the Read category at low severity since directory listing poses minimal risk even if misused by an agent.

From the tool's own definition: "Tool name and description indicate it 'List files and directories' with no modification capability. The server description emphasizes 'read files' and 'safe, configurable root' access patterns."

Risk signals: Accepts file system path (path)

## Use case

AI agents call list_directory to retrieve information from Dev 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 Dev:

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

## Other tools on Dev (6)

- `get_file_info` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/get-file-info.md
- `read_text_file` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/read-text-file.md
- `search_files` — Read — https://policylayer.com/tools/deep-ai-kr-dev-mcp/search-files.md
- `create_directory` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/create-directory.md
- `move_file` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/move-file.md
- `write_file` — Write — https://policylayer.com/tools/deep-ai-kr-dev-mcp/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=deep-ai-kr-dev-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/deep-ai-kr-dev-mcp