Argus Match Filter Search Translator MCP Tools#
This document describes the MCP tools available for Argus match filter search translation.
These tools help users:
build an Argus match filter search query payload
discover valid values for match filter event flags
discover valid values for match filter sorting
validate search pagination, event flags, and sort fields before retrieving results
General Notes#
Use these tools when you want the LLM to turn your match-filter search intent into a valid search query.
Argus match filters define detection rules that identify relevant events from the real-time security event stream and can transform matching events.
Describe what you want to find in plain language, and the LLM can use the request fields in this document to build the search.
If your request involves event flags or sorting, the LLM can look up the allowed values before building the query.
This applies to
includeEventFlag,excludeEventFlag, andsortBy.Returned allowed values are case-sensitive, so the LLM should keep them exactly as returned.
If you want actual search results after building the query, the LLM can then use the match filter search execution tool with the same search intent.
Tool: generateArgusMatchFilterSearchQuery#
Purpose
Generate an Argus match filter search query from your search intent. The result is the generated match filter search JSON.
Arguments
Argument: request#
High-level purpose: the full match filter search definition the LLM builds from your request.
Type:
objectRequired: Yes
Default: None
request fields#
Field |
Description |
Type |
Default |
Required |
|---|---|---|---|---|
|
Match filters by any of these filter IDs. |
|
None |
No |
|
Match filters belonging to any of the specified customers, using customer ID or short name. |
|
None |
No |
|
When customer filtering is used, also include parent customers. |
|
|
No |
|
When customer filtering is used, also include child customers. |
|
|
No |
|
Match filter flags that must all be present. Allowed values: |
|
None |
No |
|
Match filter flags that must not be present. Exclusion still applies even if included flags match. Allowed values: |
|
None |
No |
|
Match filter types to include. Allowed values: |
|
None |
No |
|
Match filters associated with any of these case IDs. |
|
None |
No |
|
Match filters targeting any of these alarm IDs. |
|
None |
No |
|
Match filters targeting any of these attack categories, using ID or short name. |
|
None |
No |
|
Match filters for any of these sensor locations, using ID or short name. |
|
None |
No |
|
Argus event flags that must be associated with the match filter. When this filter is involved, the LLM can look up the allowed flag values behind the scenes. |
|
None |
No |
|
Argus event flags that must not be associated with the match filter. When this filter is involved, the LLM can look up the allowed flag values behind the scenes. |
|
None |
No |
|
Keyword-based matching across match filter fields. |
|
None |
No |
|
Time-based narrowing for match filter search. |
|
None |
No |
|
Whether match and transform code should be included in the result objects. |
|
|
No |
|
Pagination settings. |
|
|
No |
|
Sort order list. Use list order as priority. Prefix with |
|
None |
No |
request.keywordFilter fields#
Field |
Description |
Type |
Default |
Required |
|---|---|---|---|---|
|
Search terms to match. |
|
None |
No |
|
Which match filter keyword fields to search. Allowed values: |
|
|
No |
|
How to evaluate multiple keywords. Allowed values: |
|
|
No |
request.timeFilter fields#
Field |
Description |
Type |
Default |
Required |
|---|---|---|---|---|
|
Which match filter time field(s) the range applies to. Allowed values: |
|
|
No |
|
Start of the time range. Accepts epoch millis as string, ISO-8601 UTC, or relative expressions such as |
|
None |
No |
|
End of the time range. Accepts epoch millis as string, ISO-8601 UTC, or relative expressions such as |
|
|
No |
|
How to evaluate multiple |
|
|
No |
request.page fields#
Field |
Description |
Type |
Default |
Required |
|---|---|---|---|---|
|
Maximum number of items per page. Accepted range: |
|
|
No |
|
Number of items to skip before returning results. Must be |
|
|
No |
Usage notes
Match filter search pagination supports
1to100items per page. Values outside that range will fail.For descending sorting, the LLM can use a
-prefix such as-validFrom.matchAnyEventis a distinct filter type for filters explicitly configured for both raw and aggregated events. It is not a shortcut for selecting raw and aggregated filters together.To search for event property existence, the LLM can use
propertyKey. To search for event property values, it can usepropertyValue.Ask explicitly if you want match and transform code excluded from search results, since code is included by default.
Tool: listArgusMatchFilterSearchSortBy#
Purpose
Return the allowed sortBy values for Argus match filter search.
Arguments
This tool takes no arguments.
Current returned values
id, name, validFrom, validTo, created, lastUpdated
Tool: listMatchFilterArgusEventFlags#
Purpose
Return the allowed event flag values for Argus match filter search.
Arguments
This tool takes no arguments.
Current returned values
ESTABLISHED, BLOCKED, SNAPSHOT, FINALIZED, SOURCE_IS_CUSTOMERNET, DESTINATION_IS_CUSTOMERNET, SOURCE_IS_PARTIAL_CUSTOMERNET, DESTINATION_IS_PARTIAL_CUSTOMERNET, PARTIALLY_BLOCKED, FALSE_POSITIVE, NOT_A_THREAT, TUNING_CANDIDATE, NOTIFIED, PARTIALLY_NOTIFIED, FOLLOWUP, IDENTIFIED_THREAT, THREAT_CANDIDATE, ACKNOWLEDGED, PARTIALLY_ACKNOWLEDGED, SEVERITY_ADJUSTED, COMMENTED, FILTERED, CHECKED, INCOMPLETE_DETAILS, AGGREGATED_BASE_EVENT, REMOTE_STORAGE, CUSTOM_SOURCE_AGGREGATION, CUSTOM_DESTINATION_AGGREGATION, ASSOCIATED_TO_CASE_BY_FILTER, SEVERITY_INCREASED_BY_FILTER, SEVERITY_REDUCED_BY_FILTER, CREATED_BY_ANALYSIS_FILTER, IP_INVERTED_BY_FILTER, HAS_PAYLOAD, HAS_PCAP, EXTEND_EVENT_TTL, INITIAL_TUNING, PARTIAL_INITIAL_TUNING, POST_ANALYSIS, SSL_TERMINATED, PARTIAL_SSL_TERMINATED, AUTO_REPORT, MISSING_TIMESTAMP, CLOCK_OUT_OF_SYNC, DROP_ANALYSIS, ESCALATED_BY_REPUTATION, HAS_SAMPLE, STORE_EVENT, STORE_AGGREGATED, EVENT_FROM_OT_ENVIRONMENT, EVENT_FROM_RESTRICTED_IT_ENVIRONMENT, FAILURE