Get Alert Rule
get_alert_ruleRetrieve a Sentry alert rule by ID or exact name to inspect its triggers, conditions, notification actions, connected monitors, and project scope.
Instructions
Get one Sentry alert rule by ID or exact name: its triggers, conditions, notification actions, connected monitors, and project scope. Prefer get_metric_monitor_details for Metric Monitors; cron and uptime monitors have their own get tools.
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": {
"ruleIdOrName": "<ruleIdOrName>"
},
"name": "get_alert_rule"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | Alert family: `issue` for Alerts (workflows), `metric` for Metric Monitors. `all` matches by exact name only. | all |
| fresh | No | Bypass cached reads. | |
| regionUrl | No | ||
| projectSlug | No | ||
| ruleIdOrName | Yes | Alert ID or exact name. With `metric`, a number is a legacy alert-rule ID; use detector:<id> for a Metric Monitor ID. With `all`, digits are matched as a name. | |
| organizationSlug | No | The organization slug, from `find_organizations`. In `org/project` notation, the part before the slash. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| guidance | No | ||
| alertRule | No | Set when the match is an Issue Alert. | |
| metricMonitor | No | Set when the match is a Metric Monitor. |