List all allowed directory roots for filesystem operations.
AI agents call list_allowed_directories 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 retrieves configuration information about sandbox boundaries. It performs no write, execute, or destructive operations—it only queries and returns data about which directories are accessible. The severity is low because disclosure of sandbox boundaries is informational and does not directly compromise data or systems, though it could inform further reconnaissance.
From the tool's definition Tool name 'list_allowed_directories' and description 'List all allowed directory roots' indicate a query/retrieval operation with no modification or execution of side effects.
Attacks that exploit this kind of access
List all allowed directory roots for filesystem operations. 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_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 Filesystem MCP Server. 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 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 →