List alert rules

curl "https://herculradar.com/api/v1/alerts" \
  --header "Authorization: Bearer hr_live_…"

Tool name list_alerts. It takes the same input and returns the same { data, meta } envelope as REST, because both call the same function.

List alert rules — what triggers a notification and where it is sent.

{
  "data": {
    "alerts": [
      {
        "id": "uuid",
        "name": "Critical complaints",
        "channel": "email",
        "destination": "team@acme.dev",
        "categories": [
          "complaint"
        ],
        "min_urgency": 70,
        "active": true
      }
    ]
  },
  "meta": {
    "capability": "list_alerts",
    "requestId": "req_9f2b4a8c1d0e",
    "idempotencyReplayed": false,
    "docs": "https://herculradar.com/docs/reference/list_alerts"
  }
}

Requires the alerts:read scope. A credential without it gets 403 FORBIDDEN. Resources in projects the credential cannot reach answer 404 NOT_FOUND rather than 403, so ids cannot be probed across tenants.