Lists all available WSL distributions and shows which one is currently being used.
AI agents call list_wsl_distributions to retrieve information from Filesystem MCP Server for WSL without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a simple informational query that returns metadata about WSL distributions. It has no side effects, cannot modify system state, and poses minimal risk even if misused by an AI agent. The worst outcome would be information disclosure about what distributions are installed, which is benign.
From the tool's definition Tool name 'list_wsl_distributions' and description 'Lists all available WSL distributions and shows which one is currently being used' indicate a read-only operation that retrieves information about installed distributions without modifying, executing, or…
Documented attack patterns abuse exactly the kind of access list_wsl_distributions gives an agent:
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_wsl_distributions:
{
"version": "1",
"default": "deny",
"tools": {
"list_wsl_distributions": {}
}
} list_wsl_distributions 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.
Lists all available WSL distributions and shows which one is currently being used. It is categorised as a Read tool in the Filesystem MCP Server for WSL MCP Server, which means it retrieves data without modifying state.
Register the Filesystem MCP Server for WSL MCP server in PolicyLayer and add a rule for list_wsl_distributions: 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.
list_wsl_distributions 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_wsl_distributions 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_wsl_distributions. 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_wsl_distributions 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.
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.
Free to start. No card required.
14 Filesystem MCP Server for WSL tools catalogued and risk-classified — across an index of 43,000+ MCP servers.