AI agents call get_running_processes to retrieve information from MCPHub without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves process metadata without side effects. However, it accesses sensitive system information that could inform privilege escalation or reconnaissance attacks, elevating severity above 'low'. Medium severity reflects the reconnaissance value to an adversary, while Read category is appropriate because the operation itself cannot modify system state.
From the tool's definition Tool name 'get_running_processes' indicates retrieval of system process information with no modification capabilities. The empty description limits specificity, but the verb 'get' and absence of destructive/write language strongly suggest query-only behavior.
Attacks that exploit this kind of access
get_running_processes. It is categorised as a Read tool in the MCPHub MCP Server, which means it retrieves data without modifying state.
Register the MCPHub 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 MCPHub. 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 MCPHub MCP server (jayden-dong/mcphub). 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 →