Get a list of running processes with resource usage
AI agents call get_processes to retrieve information from Multi-Tool MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about running processes and their resource consumption. It has no side effects, does not execute code or commands, does not modify data, and does not delete anything. It is a straightforward read operation that retrieves system state information for monitoring or observational purposes.
From the tool's definition Tool name 'get_processes' and description 'Get a list of running processes with resource usage' indicate a read-only query operation that retrieves system information without modifying or executing anything.
Attacks that exploit this kind of access
Get a list of running processes with resource usage. It is categorised as a Read tool in the Multi-Tool MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Tool MCP Server MCP server in PolicyLayer and add a rule for get_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 Multi-Tool MCP Server. Nothing to install.
get_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_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_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_processes is provided by the Multi-Tool MCP Server MCP server (shawn-falconbury/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 →