Before you start
- An Iru API token with MCP turned on and permissions that cover the calls below (recipe 1).
- The EDR add-on, with devices on Blueprints that have EDR turned on.
Prompt for your agent
Pull threat details from Iru with GET /api/v2/threat/threat-details and behavioral detections with GET /api/v2/threat/behavioral-detections/events. Keep only events from the last 7 days, using the dates in the response. Summarize them by severity, classification and status, list the affected devices, and tell me which date field you filtered on.
Steps
Pull file threats
Version 2 adds severity, tags and management state. The docs list no date parameter, so the agent keeps this week's events from the response.
GET/api/v2/threat/threat-detailsSource: Iru API: Get Threat Details - v2
Pull behavioral detections
Pull behavioral detections the same way and keep this week's events.
GET/api/v2/threat/behavioral-detections/eventsWrite the summary
Group by Severity (Critical, High, Medium, Low, Informational), Classification and Status (New, Open, Closed, Archived).
In the web app, open Detections, set Viewing to Last 7 days and select Export for a CSV with the same filters.
Source: Understanding threat events
Common pitfalls
- On Windows, EDR runs in Detect posture only, with file-based detection only.
- A threat's classification can change after you pull it.
FAQ
What does the agent need to summarize EDR threats?
The EDR add-on and a token that covers GET /api/v2/threat/threat-details and GET /api/v2/threat/behavioral-detections/events. Version 2 adds severity, tags and management state.
Can I pull only the last 7 days?
The calls have no documented date parameter, so the agent filters by date from the response.
Which severities and statuses can a threat have?
Severities are Critical, High, Medium, Low and Informational. Statuses are New, Open, Closed and Archived. A classification can change after you pull it.
Does it cover Windows?
Yes. On Windows, EDR runs in Detect posture only, with file-based detection only.