List running processes with CPU and memory usage.
AI agents call list_processes to retrieve information from Linux 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 and queries running process data without side effects. It aligns with the 'Read' category as it fetches system state information for diagnostic purposes. Severity is low because process listing exposes only runtime system state information that does not enable harmful actions on its own; actual process termination or code execution would require separate Execute or Destructive tools.
From the tool's definition Tool name 'list_processes' and description 'List running processes with CPU and memory usage' indicate retrieval of process information. Server description emphasizes 'read-only Linux system diagnostics' with no capability to modify or terminate processes.
Attacks that exploit this kind of access
List running processes with CPU and memory usage. It is categorised as a Read tool in the Linux MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Linux 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 Linux 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 Linux MCP Server MCP server (narmaku/linux-mcp-server-archived). 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 →