Get processes grouped by name with instance counts
AI agents call get_process_instances 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 query operation that retrieves system process metadata and aggregates it by name. It has no capability to modify, delete, or execute processes—only to observe and report on them. This is a standard read/query operation with no destructive or irreversible impact.
From the tool's definition Tool retrieves and groups process information with instance counts. The description explicitly states it 'Get processes' (retrieves data) with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get processes grouped by name with instance counts. 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_instances: 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_instances 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_instances 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_instances. 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_instances 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 →