zscaler-mcp-server

Official

by zscaler

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

zins_get_cyber_incidents

Read-only

Get cyber-security incidents grouped by category. Read-only analytics.

Instructions

Get cyber-security incidents grouped by category. Read-only analytics.

Groups incidents by one or more dimensions (default THREAT_CATEGORY_ID); multi-dimension groupings surface their breakdown under nested entries. An empty result means no incidents were detected. Window must be a 7- or 14-day historical interval.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response.
`end_time`	No
`start_time`	No
`end_days_ago`	No
`categorize_by`	No
`start_days_ago`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.15.3Aug 19, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / categorize_by / title
```
Added value: +"Categorize By"
```
addedInput schema / properties / end_days_ago / title
```
Added value: +"End Days Ago"
```
addedInput schema / properties / end_time / title
```
Added value: +"End Time"
```
addedInput schema / properties / limit / title
```
Added value: +"Limit"
```

changedInput schema / properties / query / description

Previous value: -"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response."

addedInput schema / properties / query / title
```
Added value: +"Query"
```
addedInput schema / properties / start_days_ago / title
```
Added value: +"Start Days Ago"
```
addedInput schema / properties / start_time / title
```
Added value: +"Start Time"
```

addedInput schema / title

Added value: +"zins_get_cyber_incidentsArguments"

Changed16 schema fields changedv0.14.0Jul 28, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / categorize_by / description

Removed value: -"Categories to group incidents by. Values: THREAT_CATEGORY_ID, APP_ID, USER_ID, TIME, SRC_COUNTRY. Default: ['THREAT_CATEGORY_ID']"

removedInput schema / properties / categorize_by / title
```
Removed value: -"Categorize By"
```

removedInput schema / properties / end_days_ago / description

Removed value: -"Days ago for end. Default: 2 (data has 24-48hr delay). Interval = start_days_ago - end_days_ago must be 7 or 14."

removedInput schema / properties / end_days_ago / title
```
Removed value: -"End Days Ago"
```

removedInput schema / properties / end_time / description

Removed value: -"ALTERNATIVE: End time as Unix epoch in MILLISECONDS. Only use if you need a specific timestamp. Overrides end_days_ago."

removedInput schema / properties / end_time / title
```
Removed value: -"End Time"
```

removedInput schema / properties / limit / description

Removed value: -"Maximum number of incident entries to return (1-1000)."

removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."
+}

removedInput schema / properties / start_days_ago / description

Removed value: -"Days ago for start. API requires EXACTLY 7 or 14 day intervals. Default: 16 (with end_days_ago=2 gives 14-day interval). For 7-day: use 9. For 14-day: use 16."

removedInput schema / properties / start_days_ago / title
```
Removed value: -"Start Days Ago"
```

removedInput schema / properties / start_time / description

Removed value: -"ALTERNATIVE: Start time as Unix epoch in MILLISECONDS. Only use if you need a specific timestamp. Overrides start_days_ago."

removedInput schema / properties / start_time / title
```
Removed value: -"Start Time"
```

removedInput schema / title

Removed value: -"zins_get_cyber_incidentsArguments"

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "items": {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      "title": "Result",
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "zins_get_cyber_incidentsOutput",
-  "type": "object"
-}New value: +null

First observedv0.12.7Jun 24, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the 'Read-only analytics' phrase is redundant but not contradictory. The description adds valuable behaviors: grouping by multiple dimensions surfaces nested `entries`, empty result means no incidents, and the time window restriction. This goes beyond annotation-provided safety information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the primary purpose, and every sentence adds critical information: grouping default, nested structure, empty-result semantics, and time window restriction. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 7 parameters, no output schema, and many close siblings, the description provides enough information to select and invoke it correctly. It covers grouping behavior, output structure (nested entries), and time constraints. It does not detail return formats or error behavior, but the essential context for choosing this tool is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is low (14%), so the description compensates by explaining the key `categorize_by` parameter (one or more dimensions, default THREAT_CATEGORY_ID) and the relationship between start/end time parameters (7- or 14-day window). It does not cover `limit` or `query`, but `query` already has a thorough schema description. This adds meaning for the most critical parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets cyber-security incidents grouped by category, with a specific default grouping (THREAT_CATEGORY_ID) and support for multiple dimensions. This distinguishes it from sibling tools like zins_get_cyber_incidents_by_location and zins_get_cyber_incidents_daily, which are specialized variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides clear usage context: read-only analytics, historical 7- or 14-day window, and grouping behavior. However, it does not explicitly state when to prefer this generic tool over its specialized siblings (e.g., by_location, by_threat_and_app), nor mention exclusions. The context is strong but alternative guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

zins_get_cyber_incidents

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools