Display all directories currently accessible to the server.
AI agents call list_allowed_directories 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 retrieves information about accessible directories—a passive, non-destructive query with no side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal; an agent gaining a list of allowed directories cannot directly harm data or systems, though it could inform further malicious actions. Classified as Read with low severity.
From the tool's definition Tool name 'list_allowed_directories' and description 'Display all directories currently accessible to the server' indicate a read-only query operation that retrieves and enumerates filesystem metadata without modification.
Documented attack patterns abuse exactly the kind of access list_allowed_directories 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_allowed_directories:
{
"version": "1",
"default": "deny",
"tools": {
"list_allowed_directories": {}
}
}list_allowed_directories 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.
Display all directories currently accessible to the server. 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_allowed_directories: 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_allowed_directories 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_allowed_directories 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_allowed_directories. 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_allowed_directories 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.