List directory contents with flexible output formats. Replaces the previous
AI agents call list_directory to retrieve information from Vulcan File Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—enumerating directory contents. It has no side effects, cannot modify, delete, or execute code. The blast radius of misuse is minimal: an attacker gains visibility into the filesystem structure but cannot alter or execute anything. Belongs to the Read category alongside sibling tools like 'list_allowed_directories' and 'get_file_info'.
From the tool's definition Tool name 'list_directory' and description 'List directory contents with flexible output formats' indicate a query operation that retrieves and displays filesystem information without modification.
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 Vulcan File Ops, 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 contents with flexible output formats. Replaces the previous. It is categorised as a Read tool in the Vulcan File Ops MCP Server, which means it retrieves data without modifying state.
Register the Vulcan File Ops 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 Vulcan File Ops. 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 Vulcan File Ops MCP server (n0zer0d4y/vulcan-file-ops). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Vulcan File Ops, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 Vulcan File Ops tools catalogued and risk-classified — across an index of 43,000+ MCP servers.