Skip to content

Detections

Accessing and analyzing CrowdStrike Falcon detections

  • Alerts: READ
  • Alerts: WRITE

Required scopes: Alerts: READ

Retrieve details for detection IDs you already have.

Use when you have specific composite detection ID(s). For discovering detections by criteria (severity, status, hostname, etc.), use falcon_search_detections instead. Returns full detection records.

Example prompts:

  • “Get me the details for this detection”

Required scopes: Alerts: READ

Find detections by criteria and return their complete details.

Use this to discover detections by severity, status, hostname, time range, or other attributes. Consult falcon://detections/search/fql-guide before constructing filter expressions. Returns full alert records including process context, device info, tactic/technique details, and threat classification.

Example prompts:

  • “Show me new high severity detections from the last 7 days”
  • “Find all unassigned critical detections”

Required scopes: Alerts: WRITE

Update the status, assignment, visibility, or verdict of one or more detections.

Use to change status (new, in_progress, reopened, closed), assign to a user by UUID, email address, or full name, append a comment, unassign, hide/show detections in the UI, or set a verdict (true_positive, false_positive, ignored). At least one update parameter must be provided. Returns [] (empty list) on success; returns an error dict on failure.

Example prompts:

  • “Mark detection abc123 as in_progress”
  • “Assign detection abc123 to analyst@example.com
  • “Close these detections and add a comment: resolved via playbook”
  • falcon://detections/search/fql-guide: Contains the guide for the filter param of the falcon_search_detections tool.