AI agents use post_silence to create or update resources in Alertmanager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alertmanager environment.
This tool creates or modifies silence rules in Alertmanager, which are reversible configuration changes. It does not delete data (would be Destructive), execute arbitrary commands (would be Execute), or move money (would be Financial). The severity is medium because silencing alerts could mask critical system issues if misused by an AI agent, creating operational risk, but the action itself is reversible.
From the tool's definition Tool name 'post_silence' and description 'Post a new silence or update an existing one' indicate creation or modification of silence rules in Alertmanager.
Documented attack patterns abuse exactly the kind of access post_silence 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 post_silence:
{
"version": "1",
"default": "deny",
"tools": {
"post_silence": {
"limits": [
{
"counter": "post_silence_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}post_silence stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Post a new silence or update an existing one. It is categorised as a Write tool in the Alertmanager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alertmanager MCP server in PolicyLayer and add a rule for post_silence: 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.
post_silence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the post_silence 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 post_silence. 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.
post_silence 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.