investigate-incident

investigate-incident is a command for Claude Code from zscaler/zscaler-mcp-server. It costs 27 tokens per session (499 once invoked), scanned A, original, MIT.

A command for investigating security incidents with Z-Insights, using threat, firewall, web-traffic, and unsanctioned-application data.

In plain words
What is it for?
It helps search for threats such as malware or phishing, review cyber incidents and firewall actions, examine web-traffic patterns, and identify unsanctioned applications.
Why use it?
It brings several security data sources together so administrators can connect suspicious activity with blocked or allowed traffic and shadow IT, meaning unapproved software or services.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the zscaler plugin — 42 skills, 20 commands, 1 MCP server shipped together

Good fit It helps search for threats such as malware or phishing, review cyber incidents and firewall actions, examine web-traffic patterns, and identify unsanctioned applications.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zscaler/zscaler-mcp-server/investigate-incident
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/zscaler/zscaler-mcp-server

Made for: Claude Code.

Or install zscaler, the plugin that ships this one along with the rest of its 42 skills, 20 commands, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for investigate-incident

README.md
[![agentmods](https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-incident/github.svg)](https://agentmods.dev/commands/zscaler/zscaler-mcp-server/investigate-incident)
Your own site
<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/investigate-incident"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-incident/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for investigate-incident

Your own site · 80×15
<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/investigate-incident"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/investigate-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 499 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.00499
Opus 5 $0.00014 $0.00249
Sonnet 5 $0.00005 $0.00100
Haiku 4.5 $0.00003 $0.00050

Measured 11d ago against content hash 86fea8387907, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

investigate-incident scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/investigate-incident.md · 99 lines

What it actually says

Investigate Security Incident

Investigate: $ARGUMENTS

Step 1: Parse Input

Extract:

  • Threat type or keyword (e.g., "malware", "phishing", "ransomware", a specific IP or domain)
  • Time window in hours (default: 24)

Step 2: Check Threat Categories

zins_get_threat_categories()
```text

Identify the most active threat categories in the environment.

## Step 3: Get Cyber Incident Data

```text
zins_get_cyber_incidents()
```text

Look for incidents matching the threat type or keyword.

## Step 4: Analyze Firewall Actions

```text
zins_get_firewall_actions()
zins_get_firewall_insights()
```text

Check for blocks, allows, and suspicious connection patterns.

## Step 5: Review Web Traffic Patterns

```text
zins_get_web_traffic_overview()
zins_get_web_application_usage()
```text

Look for unusual traffic spikes or suspicious application usage.

## Step 6: Check Shadow IT

```text
zins_get_shadow_it_summary()
zins_get_saas_security_posture()
```text

Identify unsanctioned applications that may have been used in the incident.

## Step 7: Present Investigation Report

```text
Security Incident Investigation
==================================

Timeframe: <start> to <end>
Focus: <threat_type>

THREAT SUMMARY:
  Active threat categories: <list>
  Incidents detected: X
  Firewall blocks: Y

INCIDENT TIMELINE:
  <chronological list of events>

AFFECTED ASSETS:
  Users: <list>
  Devices: <list>
  Applications: <list>

FIREWALL ANALYSIS:
  Blocked connections: X
  Allowed suspicious: Y (review needed)

SHADOW IT FINDINGS:
  Unsanctioned apps detected: <list>

ROOT CAUSE ASSESSMENT:
  <analysis>

RECOMMENDED ACTIONS:
  1. <immediate action>
  2. <containment action>
  3. <follow-up investigation>
```text
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 99 lines · 27 tokens per session scan A 86fea8387907

Subscribe to this mod's changes

investigate-incident is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 499 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.