Return process group names from process monitoring metrics.
AI agents call list_process_groups to retrieve information from MCP Prometheus 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 process group names from pre-existing metrics without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval operation consistent with other Read-category tools on this server (list_checks, list_environments, list_servers, etc.).
From the tool's definition Tool name 'list_process_groups' and description 'Return process group names' indicate retrieval of existing monitoring data with no modification or execution capability.
Attacks that exploit this kind of access
Return process group names from process monitoring metrics. It is categorised as a Read tool in the MCP Prometheus MCP Server, which means it retrieves data without modifying state.
Register the MCP Prometheus MCP server in PolicyLayer and add a rule for list_process_groups: 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 MCP Prometheus. Nothing to install.
list_process_groups 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 list_process_groups 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 list_process_groups. 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.
list_process_groups is provided by the MCP Prometheus MCP server (yeonkyu-git/mcp-prometheus-loki). 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 →