List contents of a directory. Returns file and directory information including names, types, sizes, and modification dates.
AI agents call list_directory to retrieve information from MCP Local File Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays directory metadata (names, types, sizes, modification dates) without modifying, executing, or deleting anything. It is a standard read operation with minimal blast radius if misused by an AI agent — worst case, it reveals filesystem structure the agent already has permission to access.
From the tool's definition Tool description states 'List contents of a directory' and 'Returns file and directory information' — a pure query operation with no side effects.
Attacks that exploit this kind of access
List contents of a directory. Returns file and directory information including names, types, sizes, and modification dates. It is categorised as a Read tool in the MCP Local File Reader MCP Server, which means it retrieves data without modifying state.
Register the MCP Local File Reader 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 MCP Local File Reader. 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 MCP Local File Reader MCP server (yryuu/mcp-localfile-all-read). 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 →