List currently running processes on the system. On Unix/macOS uses
AI agents call list_processes to retrieve information from MCP PC Control Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves system state information (running processes) with no side effects. While this is informational rather than dangerous in isolation, it carries medium severity because process enumeration is valuable reconnaissance for an AI agent to identify what services are running and potentially target them with other tools (e.g., execute_command).
From the tool's definition Tool is described as 'List currently running processes on the system.' This is a read-only operation that retrieves information about running processes without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List currently running processes on the system. On Unix/macOS uses. It is categorised as a Read tool in the MCP PC Control Server MCP Server, which means it retrieves data without modifying state.
Register the MCP PC Control 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 MCP PC Control 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 MCP PC Control Server MCP server (koopatroopa787/first_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 →