list_incidents

List incidents (triggered alerts) on the platform.

List incidents (triggered alerts) on the platform.

Read-only · Calls external systems. Safe to call: this tool does not modify data.

Parameters

FieldTypeRequiredDescription
alert_idstringNoComma-separated alert definition IDs
closed_date_afterstringNoISO datetime: only incidents closed after this time
closed_date_beforestringNoISO datetime: only incidents closed before this time
created_afterstringNoISO datetime: only incidents created after this time
created_beforestringNoISO datetime: only incidents created before this time
detailbooleanNoReturn full JSON instead of compact summaries (default: false)
operatorstringYesOperator slug
pagenumberNoPage number (default 1)
statusstring (OPEN | CLOSED | MANUALLY_CLOSED | CHANGED | DEACTIVATED)NoFilter by status: OPEN, CLOSED, MANUALLY_CLOSED, CHANGED, DEACTIVATED

Example arguments

Illustrative arguments an agent supplies when calling this tool:

{
  "operator": "string"
}

Description

Incidents are created when a platform alert definition fires. They track the lifecycle from OPEN to CLOSED.

NOT the same as evaluate_alert which performs local on-demand analytics. To manage platform alerts, use list_alert_definitions.

Filters: status (OPEN/CLOSED/MANUALLY_CLOSED/CHANGED/DEACTIVATED), alert_id (comma-sep), created_after/before, closed_date_after/before.

What's next?

All MCP tools

Browse the full tool reference by category.

Connect a client

Point Claude, Cursor, or Claude Code at the server.

Last updated on