list_directory
Get a detailed listing of all files and directories in a specified path. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is essential for understanding directory structure and finding specific files within a directory. Only works within allowed ...
This record as markdown: /tools/filesystem/list-directory.md
What list_directory does on Filesystem
AI agents call list_directory 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 |
Parameters from the server's own tool schema.
Why list_directory is rated Low
This tool retrieves and queries directory contents without creating, modifying, deleting, or executing anything. It is a straightforward directory enumeration operation with no capability to alter state or trigger external actions. The restriction to allowed directories further mitigates risk.
From the tool's definition Tool name is 'list_directory' and description states it 'Get[s] a detailed listing of all files and directories in a specified path' with results that 'distinguish between files and directories'.
Risk signalsAccepts file system path (path) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_directory 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 list_directory, this is the rule to start with:
list_directory 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 list_directory call is checked against it from then on.
Questions about list_directory
Get a detailed listing of all files and directories in a specified path. Results clearly distinguish between files and directories with [FILE] and [DIR] prefixes. This tool is essential for understanding directory structure and finding specific files within a directory. 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.
list_directory accepts 1 parameter: path. 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 list_directory: 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.
list_directory 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 list_directory 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 list_directory. 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.
list_directory 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