list_processes
List all running processes. Returns process information including PID, command name, CPU usage, and memory usage. ${CMD_PREFIX_DESCRIPTION}
This record as markdown: /tools/desktop-commander/list-processes.md
What list_processes does on Desktop Commander
AI agents call list_processes to retrieve information from Desktop Commander without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_processes is rated Low
This tool queries and returns process information without modifying, executing, or deleting anything. It is fundamentally a read operation. Severity is medium (not low) because process listings can reveal sensitive information about running services, credentials in command-line arguments, or system architecture that could aid an attacker in reconnaissance or privilege escalation planning, even though the tool itself…
From the tool's definition Tool name 'list_processes' and description 'List all running processes' with output of 'process information including PID, command name, CPU usage, and memory usage' indicates a read-only retrieval operation.
Attacks that exploit this kind of access
The rule that runs list_processes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Desktop Commander, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_processes, this is the rule to start with:
list_processes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Desktop Commander, apply this rule, and every list_processes call is checked against it from then on.
Questions about list_processes
List all running processes. Returns process information including PID, command name, CPU usage, and memory usage. ${CMD_PREFIX_DESCRIPTION}. It is categorised as a Read tool in the Desktop Commander MCP Server, which means it retrieves data without modifying state.
Register the Desktop Commander 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 Desktop Commander. 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 Desktop Commander MCP server (wonderwhy-er/DesktopCommanderMCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Desktop Commander, and thousands of servers like it.
This server
Across the catalogue