AI agents call list_processes to retrieve information from Mcp Wsl Exec without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves process state information without side effects, triggering external operations, modifying data, or causing deletion. It is a straightforward enumeration/list operation. Despite being on an 'exec' server, this particular tool performs read-only system information gathering.
From the tool's definition Tool description states 'List running processes in WSL' - a read-only operation that retrieves process information without modification or execution.
Documented attack patterns abuse exactly the kind of access list_processes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Wsl Exec, and nothing reaches the server without passing your rules. This is the rule we recommend for list_processes:
{
"version": "1",
"default": "deny",
"tools": {
"list_processes": {}
}
}list_processes 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 running processes in WSL. It is categorised as a Read tool in the Mcp Wsl Exec MCP Server, which means it retrieves data without modifying state.
Register the Mcp Wsl Exec MCP server in PolicyLayer and add a rule for list_processes: 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 Mcp Wsl Exec. Nothing to install.
list_processes 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_processes 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_processes. 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_processes is provided by the Mcp Wsl Exec MCP server (spences10/mcp-wsl-exec). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Wsl Exec, 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.
7 Mcp Wsl Exec tools catalogued and risk-classified — across an index of 43,000+ MCP servers.