findings_search
Search eSentire detections and alerts within a date range. Apply filters like severity or assignee to find relevant security findings.
Instructions
Search eSentire Findings (detections/alerts) for a date range.
This is the API behind the Findings table in the Atlas platform.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "findings_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. Atlas rejects the request without it, so this defaults to 1 rather than being omitted. | |
| query | No | Filter predicates as native objects -- they are JSON+URL encoded for you. Example: [{"field": "SEVERITY", "op": "in", "value": ["Critical", "High"]}] | |
| sorts | No | Sort spec, e.g. [{"field": "event_created", "direction": "desc"}] | |
| use_v2 | No | Opt into the V2 query engine. Required for assignee_email. | |
| end_date | No | Inclusive end, YYYY-MM-DD. | |
| per_page | No | Results per page. Also mandatory upstream; defaults to 50. | |
| start_date | No | Inclusive start, YYYY-MM-DD. | |
| customer_code | No | Tenant code. Falls back to ESENTIRE_CUSTOMER_CODE. | |
| assignee_email | No | Filter by assignee. Only honoured when use_v2 is true -- it is silently ignored otherwise, so this tool sets use_v2 for you. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |