List all tracked processes (running, completed, failed, etc.)
AI agents call list_processes to retrieve information from Run Command 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 information about previously executed processes and their status. It performs no side effects, does not execute commands, and does not modify system state. While the server overall provides Execute capabilities (start_async_command, get_command_output), this specific tool is limited to observing tracked process metadata.
From the tool's definition Tool name 'list_processes' and description 'List all tracked processes' indicate a read-only operation that queries process state without modifying or executing anything.
Attacks that exploit this kind of access
List all tracked processes (running, completed, failed, etc.). It is categorised as a Read tool in the Run Command MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Run Command MCP Server 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 Run Command MCP Server. 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 Run Command MCP Server MCP server (stilllovee/run-command-mcp). 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 →