zscaler-tool-conventions

zscaler-tool-conventions is a cursor rule for Cursor from zscaler/zscaler-mcp-server. It costs 298 tokens per session, scanned A, original, MIT.

Naming and usage rules for Zscaler tools that manage the Zero Trust Exchange, a service for controlling access to applications, devices, and data. The rules explain tool prefixes, string IDs, authentication settings, discovery, listing, and pagination.

In plain words
What is it for?
Use it when discovering Zscaler services, listing or inspecting resources, choosing tools for ZIA, ZPA, ZDX, and other services, or handling large result sets.
Why use it?
They make it easier to find the correct tool and avoid failed requests caused by wrong names, ID types, credentials, or incomplete lists.

Cursor rule for Cursor

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

Good fit Use it when discovering Zscaler services, listing or inspecting resources, choosing tools for ZIA, ZPA, ZDX, and other services, or handling large result sets.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/zscaler/zscaler-mcp-server/zscaler-tool-conventions
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 zscaler-tool-conventions

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/zscaler/zscaler-mcp-server/zscaler-tool-conventions"><img src="https://agentmods.dev/badge/rules/zscaler/zscaler-mcp-server/zscaler-tool-conventions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 298 This file is loaded in full into every session.
When invoked 298 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.00298 $0.00298
Opus 5 $0.00149 $0.00149
Sonnet 5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

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

Security

Grade A, and why

zscaler-tool-conventions 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 9d 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/zscaler-tool-conventions.mdc · 17 lines

What it actually says

Zscaler MCP tool conventions

When working with Zscaler MCP tools:

  1. All tools follow {service}_{verb}_{resource} naming: zia_list_locations, zpa_create_access_policy_rule, zdx_get_application.
  2. Service prefixes: zia_, zpa_, zdx_, zcc_, easm_, zins_, zid_, ztw_, zms_. Use the prefix to discover tools for a given service.
  3. Call zscaler_get_available_services first to check which services are enabled before searching for tools.
  4. IDs are always strings, even when they look numeric. Always pass IDs as strings.
  5. All tools authenticate through OneAPI (zscaler.ZscalerClient) against ZIdentity using the unified ZSCALER_CLIENT_ID / ZSCALER_CLIENT_SECRET (or ZSCALER_PRIVATE_KEY) / ZSCALER_VANITY_DOMAIN / ZSCALER_CUSTOMER_ID (ZPA only) credentials.
  6. Always list/get resources first to understand current state before creating or modifying them.
  7. List tools support page and page_size parameters. For large tenants, paginate rather than fetching everything.
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. 9d ago First seen · 17 lines · 298 tokens per session scan A 2ca964289aab

Subscribe to this mod's changes

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