system_alerts_resolve
Manually resolve the open alert for the given source+subject. Writers normally self-resolve; use this when the underlying state can no longer be observed.
This record as markdown: /tools/com-getmunin-munin/system-alerts-resolve.md
What system_alerts_resolve does on Munin
AI agents use system_alerts_resolve to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why system_alerts_resolve is rated Medium
This tool changes alert status from open to resolved, which is a reversible modification of data (alerts can typically be re-opened or the underlying issue re-flagged). It does not delete data permanently, execute arbitrary code, or move money.
From the tool's definition Tool performs 'resolve' action which modifies alert state; description states 'Manually resolve the open alert' indicating a state change operation.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_alerts_resolve safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_alerts_resolve, this is the rule to start with:
system_alerts_resolve 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every system_alerts_resolve call is checked against it from then on.
Questions about system_alerts_resolve
Manually resolve the open alert for the given source+subject. Writers normally self-resolve; use this when the underlying state can no longer be observed. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for system_alerts_resolve: 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 Munin. Nothing to install.
system_alerts_resolve 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 system_alerts_resolve 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 system_alerts_resolve. 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.
system_alerts_resolve is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Munin, and thousands of servers like it.
This server
Across the catalogue