You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(list_runtime_events): enable ML event discovery (#67)
The `list_runtime_events` tool returned zero results when querying for
ML-based detections (e.g. "Crypto Mining Detection" with `engine =
"machineLearning"`), even though these events were visible in the Sysdig
Secure UI.
The root cause was a `source != "auditTrail"` clause in the MCP
baseFilter that duplicated a filter already applied by the events API.
This duplication caused an OpenSearch query interaction that silently
excluded ML events from the `events_profiling_detection_v1` index.
Tested on both us2 and eu1 environments:
- `engine = "machineLearning"` now returns ML events (Crypto Mining
Detection confirmed)
- `source = "auditTrail"` returns 0 events (API-side filter works
correctly)
- No audit trail event leakage across 2-week windows with 200k+ total
events
Co-authored-by: Fede Barcelona <fede_rico_94@hotmail.com>
mcp.WithDescription("List runtime security events from the last given hours, optionally filtered by severity level."),
66
+
mcp.WithDescription("List runtime security events from the last given hours, optionally filtered by severity level. Includes both Falco-based and machine learning (ML) detections such as crypto mining, anomalous logins, and other ML-detected threats."),
0 commit comments