list_directory
AI agents call list_directory to retrieve information from Filesystem MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves directory contents with no side effects—a classic Read operation. Even if directory traversal is unrestricted within the sandbox, it does not modify, delete, or execute anything. The filesystem server enforces sandboxing, further limiting blast radius. Severity is low because listing directory contents is informational only.
From the tool's definition Tool name 'list_directory' and sibling operations like 'list_allowed_directories' indicate directory enumeration/listing.
Attacks that exploit this kind of access
list_directory. It is categorised as a Read tool in the Filesystem MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Filesystem MCP Server 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 MCP Server. 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 MCP server (preston-harrison/fs-mcp-py). 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 →