AI agents call list_directory to retrieve information from Claude Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
list_directory retrieves and enumerates directory contents without modifying data or executing code. It is a read-only query operation with minimal blast radius. Low severity because directory enumeration alone poses limited risk unless the codebase contains sensitive secrets, but that is an operational security issue rather than a tool capability issue.
From the tool's definition Tool name is 'list_directory'; sibling tools include 'directory_tree', 'read_file', and 'search_text' which are all read operations.
Documented attack patterns abuse exactly the kind of access list_directory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Context, and nothing reaches the server without passing your rules. This is the rule we recommend for list_directory:
{
"version": "1",
"default": "deny",
"tools": {
"list_directory": {}
}
}list_directory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
list_directory. It is categorised as a Read tool in the Claude Context MCP Server, which means it retrieves data without modifying state.
Register the Claude Context 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 Claude Context. 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 Claude Context MCP server (zilliztech/claude-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Claude Context tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Claude Context tools catalogued and risk-classified — across an index of 42,500+ MCP servers.