update alert rule

[einatmeidan]

I would like the ability to edit an existing alert rule directly from MCP.
This would make it easier to update conditions, thresholds, or other rule settings without needing to recreate the rule or make changes manually.
For example:

• add, remove, or update labels
• change the alert rule name
• adjust the pending time before an alert is triggered

[sierikov]

I had a quick look on a codebase. I can try to implement all or at least some of handlers one-by-one.

My vision is adding to tools/alerting.go following handlers in order:

• rename_alert_rule with params uid string and newTitle string - to change the alert rule name. And must be the easiest one.
• set_alert_rule_pending_duration with params: uid string, duration strfmt.Duration - this one can be tricky, but maybe I can get it done only updating ProvisionedAlertRule.For field. (If it is tricky - I will do next 2 instead, and move it to the end of the list)
• add_alert_rule_labels with params uid string and labelsToAdd map[string]string - to add labels to the rule.
• remove_alert_rule_labels with params: uid string, labelKeys []string - to remove labels from the rule.

For the last two, we should probably think about validation. If we don’t, we could just pass the input to the instance, and it’ll handle the validation for us, which would save us from duplicating the same logic. But if we want to fail on MCP level we need define rules for labels.
What do you think?

[sd2k]

@sierikov nice, thanks for looking into that. My hunch is that we should avoid adding too many different tools - we already have quite a lot - so perhaps just an 'update alert rule' tool would be sufficient.

The docs for the alerting HTTP API will certainly come in handy, probably the RoutePutAlertRule route. We can probably just rely on the endpoint itself to do validation as long as it returns suitable error messages for us to return to the model, at least to start.