Legacy compatibility - Get running processes from Linux host
AI agents call get_running_processes to retrieve information from SSH 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 the state of running processes on a Linux system without executing commands, modifying configurations, or destructively altering system state. It is a read-only operation similar to running 'ps' or 'top' for diagnostic purposes. While the parent SSH server enables dangerous operations, this specific tool is confined to information gathering with no side effects.
From the tool's definition Tool name is 'get_running_processes' with description 'Get running processes from Linux host'. The verb 'Get' and the passive query nature indicate data retrieval only. No execution, modification, or deletion of processes occurs.
Attacks that exploit this kind of access
Legacy compatibility - Get running processes from Linux host. It is categorised as a Read tool in the SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for get_running_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 SSH MCP Server. Nothing to install.
get_running_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 get_running_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 get_running_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.
get_running_processes is provided by the SSH MCP Server MCP server (inframcp/ssh-mcp-server). 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 →