check-access

check-access is a command for Claude Code from zscaler/zscaler-mcp-server. It costs 19 tokens per session (434 once invoked), scanned A, original, MIT.

A command that checks whether a particular user or group can reach a URL through Zscaler Internet Access (ZIA), a cloud service that controls company web traffic.

In plain words
What is it for?
Use it to check a person's or group's access to sites such as YouTube or Google Drive, including the URL category, matching rules, and whether access is allowed, blocked, or cautioned.
Why use it?
It replaces a manual review of several security rule sets with one access verdict. It also shows when SSL inspection, data-loss prevention, or firewall rules affect the result.

Command for Claude Code

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

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

Good fit Use it to check a person's or group's access to sites such as YouTube or Google Drive, including the URL category, matching rules, and whether access is allowed, blocked, or cautioned.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/zscaler/zscaler-mcp-server/check-access
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 28 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 check-access

README.md
[![agentmods](https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/check-access.svg)](https://agentmods.dev/commands/zscaler/zscaler-mcp-server/check-access)
Your own site
<a href="https://agentmods.dev/commands/zscaler/zscaler-mcp-server/check-access"><img src="https://agentmods.dev/badge/commands/zscaler/zscaler-mcp-server/check-access.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 434 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.00019 $0.00434
Opus 5 $0.00010 $0.00217
Sonnet 5 $0.00004 $0.00087
Haiku 4.5 $0.00002 $0.00043

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

Security

Grade A, and why

check-access 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 8d 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/check-access.md · 82 lines

What it actually says

Check User URL Access

Check access for: $ARGUMENTS

Step 1: Parse Input

Extract:

  • User or group name
  • URL to check (e.g., youtube.com, drive.google.com/upload)

Step 2: Classify the URL

zia_url_lookup(urls=["<url>"])
```text

Note the URL category classification.

## Step 3: Evaluate URL Filtering Rules

```text
zia_list_url_filtering_rules()
```text

Walk through rules in order. For each rule, check if:

- The user/group matches the rule's scope
- The URL category matches the rule's categories
- The rule's action (ALLOW, BLOCK, CAUTION, ISOLATE)

The first matching rule determines the verdict.

## Step 4: Check SSL Inspection

```text
zia_list_ssl_inspection_rules()
```text

Determine if the traffic would be inspected, which affects DLP and threat detection.

## Step 5: Check DLP Rules

```text
zia_list_dlp_web_rules()
```text

Check if any DLP rules apply to this URL category for this user.

## Step 6: Check Cloud Firewall

```text
zia_list_cloud_firewall_rules()
```text

Look for port/protocol-based rules that might affect access.

## Step 7: Present Verdict

```text
Access Verdict: ALLOWED / BLOCKED / CAUTIONED
URL: <url>
Category: <category>
User/Group: <user_or_group>

Matching Rule: "<rule_name>" (order: <N>)
Action: <action>
Reason: <explanation>

Additional Findings:
- SSL Inspection: Yes/No (rule: "<rule_name>")
- DLP: No matching rules / Matched rule "<name>"
- Firewall: No blocks / Blocked by "<rule_name>"
```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. 8d ago First seen · 82 lines · 19 tokens per session scan A 85e611ba4949

Subscribe to this mod's changes

check-access is a command published in the GitHub repository zscaler/zscaler-mcp-server (50 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 434 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.