list_allowed_directories

THE RISK

Low Risk

Why list_allowed_directories needs a policy

This tool performs a simple information retrieval operation—it lists permitted directories without side effects. It does not create, modify, delete, execute commands, or move money. The blast radius of misuse is minimal since knowing which directories are allowed does not grant access beyond what the server already restricts, and cannot be used to harm data or systems. Classified as Read with low severity.

From the tool's definition Tool name 'list_allowed_directories' and description 'Returns the list of directories that this server is allowed to access' indicate a read-only operation that queries and retrieves configuration data without modifying anything.

Documented attack patterns abuse exactly the kind of access list_allowed_directories gives an agent:

POLICY

How to control list_allowed_directories

PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem MCP Server for WSL, and nothing reaches the server without passing your rules. This is the rule we recommend for list_allowed_directories:

policy.json

{
  "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.

Create a free account and register Filesystem MCP Server for WSL — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Filesystem MCP Server for WSL tools

Write create_directory Create a new directory or ensure a directory exists. Can create multiple Write edit_file Make line-based edits to a text file. Each edit replaces exact line sequences Write move_file Move or rename files and directories. Can move files between directories Write write_file Create a new file or completely overwrite an existing file with new content. Read directory_tree Get a recursive tree view of files and directories as a JSON structure. Read get_file_info Retrieve detailed metadata about a file or directory. Returns comprehensive Read list_directory Get a detailed listing of all files and directories in a specified path. Read list_wsl_distributions Lists all available WSL distributions and shows which one is currently being used.

All 14 Filesystem MCP Server for WSL tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_allowed_directories

What does the list_allowed_directories tool do? +

Returns the list of directories that this server is allowed to access. It is categorised as a Read tool in the Filesystem MCP Server for WSL MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_allowed_directories? +

Register the Filesystem MCP Server for WSL 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 for WSL. Nothing to install.

What risk level is list_allowed_directories? +

list_allowed_directories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_allowed_directories? +

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.

How do I block list_allowed_directories completely? +

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.

What MCP server provides list_allowed_directories? +

list_allowed_directories is provided by the Filesystem MCP Server for WSL MCP server (webconsulting/mcp-server-wsl-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Filesystem MCP Server for WSL tool call.

Start from Filesystem MCP Server for WSL, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →