Get the total number of running processes
AI agents call get_process_count to retrieve information from MCProcessMonitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of system state (counting running processes). It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius if misused by an AI agent is minimal—at worst, the agent obtains basic system monitoring information. This aligns clearly with the 'Read' category for data retrieval operations.
From the tool's definition Tool name 'get_process_count' and description 'Get the total number of running processes' indicates a query operation that retrieves system information without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get the total number of running processes. It is categorised as a Read tool in the MCProcessMonitor MCP Server, which means it retrieves data without modifying state.
Register the MCProcessMonitor MCP server in PolicyLayer and add a rule for get_process_count: 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 MCProcessMonitor. Nothing to install.
get_process_count 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_process_count 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_process_count. 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_process_count is provided by the MCProcessMonitor MCP server (kiralyzoltan98/mcprocessmonitor). 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 →