zia-activation-required

zia-activation-required is a cursor rule for Cursor from zscaler/zscaler-mcp-server. It costs 91 tokens per session, scanned A, original, MIT.

A rule for ZIA configuration changes. ZIA is the system being changed, and it requires a separate activation call after creating, updating, or deleting configuration.

In plain words
What is it for?
Use it whenever an agent changes ZIA configuration. It reminds the agent to call zia_activate_configuration() after each create, update, or delete operation.
Why use it?
It prevents staged changes from being mistaken for active changes. Without activation, the update will not take effect.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it whenever an agent changes ZIA configuration. It reminds the agent to call zia_activate_configuration() after each create, update, or delete operation.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/zscaler/zscaler-mcp-server/zia-activation-required
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: Cursor.

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 zia-activation-required

README.md
[![agentmods](https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/zia-activation-required/github.svg)](https://agentmods.dev/rules/zscaler/zscaler-mcp-server/zia-activation-required)
Your own site
<a href="https://agentmods.dev/rules/zscaler/zscaler-mcp-server/zia-activation-required"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/zia-activation-required/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 zia-activation-required

Your own site · 80×15
<a href="https://agentmods.dev/rules/zscaler/zscaler-mcp-server/zia-activation-required"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/zia-activation-required.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 This file is loaded in full into every session.
When invoked 91 The same file — it is already loaded in full.
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.00091 $0.00091
Opus 5 $0.00046 $0.00046
Sonnet 5 $0.00018 $0.00018
Haiku 4.5 $0.00009 $0.00009

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

Security

Grade A, and why

zia-activation-required 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 10d 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.

rules/zia-activation-required.mdc · 9 lines

What it actually says

ZIA activation required

After any ZIA create, update, or delete operation, always call zia_activate_configuration(). Changes are staged until activation — they will not take effect without this step. This is the most common cause of "my change didn't work" issues.

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. 10d ago First seen · 9 lines · 91 tokens per session scan A c331d84c4d18

Subscribe to this mod's changes

zia-activation-required is a cursor rule published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session, about $0.0005 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.