AI agents call get-alert-groups to retrieve information from Alertmanager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves alert grouping information from Alertmanager without modifying state. It has no side effects and does not execute commands, delete data, or commit financial transactions. The 'get-' prefix and positioning among other read-only sibling tools confirm this classification.
From the tool's definition Tool name 'get-alert-groups' indicates data retrieval; sibling tools include 'get-alerts', 'get-alert-details', and 'get-silences' which are clearly read operations. Server description emphasizes 'alert retrieval' as a primary function.
Documented attack patterns abuse exactly the kind of access get-alert-groups gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Alertmanager, and nothing reaches the server without passing your rules. This is the rule we recommend for get-alert-groups:
{
"version": "1",
"default": "deny",
"tools": {
"get-alert-groups": {}
}
}get-alert-groups is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get-alert-groups. It is categorised as a Read tool in the Alertmanager MCP Server, which means it retrieves data without modifying state.
Register the Alertmanager MCP server in PolicyLayer and add a rule for get-alert-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 Alertmanager. Nothing to install.
get-alert-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 get-alert-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 get-alert-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.
get-alert-groups is provided by the Alertmanager MCP server (kaznak/alertmanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Alertmanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Alertmanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.