AI agents call get_silences 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 queries and returns information about existing silences in alertmanager without creating, modifying, or deleting any data. It is a simple read operation with minimal risk—the only potential concern would be if silence configurations contain sensitive information, but exposure of suppression rules is typically low-impact.
From the tool's definition Tool name 'get_silences' and description 'Get list of all silences' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_silences 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_silences:
{
"version": "1",
"default": "deny",
"tools": {
"get_silences": {}
}
}get_silences 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 list of all silences. 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_silences: 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_silences 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_silences 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_silences. 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_silences is provided by the Alertmanager MCP server (ntk148v/alertmanager-mcp-server). 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.
9 Alertmanager tools catalogued and risk-classified — across an index of 43,000+ MCP servers.