Set alert enabled
set_alert_enabledEnable or disable one alert. Disabling is the reversible mute: the alert and its whole firing history are kept, it still appears in the alerts list marked disabled, and any incident it still has open is settled so it stops reporting as firing. For an alert ingested from an external source (source 'external', e.g. delivered from Alertmanager) disabling also stops new incidents being created from further deliveries - but it does NOT touch the upstream Prometheus rule, which keeps firing where it is defined, so say so rather than claiming the alert itself was removed. Re-enabling resumes ingest. Find the alert id with list_alerts. Prefer this over deleting an alert: deletion also removes the firing history and cannot be undone from the portal.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"alert_id": "<alert_id>",
"enabled": "<enabled>"
},
"name": "set_alert_enabled"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| enabled | Yes | true to enable the alert, false to mute it. | |
| alert_id | Yes | Alert UUID, as returned by list_alerts. |