Zscaler Internet Access guide
Zscaler: block AI agents, AI browsers and AI tools with one custom category
AI agents act with your users' sessions, from the office and from home. Zscaler already sits in that path. Give it a custom URL category of agent domains and one rule to block it.
Next step
AI Agent Blocklist for Zscaler
AI browsers, agents, agent extension backends and MCP servers in one list you load into a ZIA custom URL category.
From $99 a month for one organisation
- Plain domain list, one domain per line, to paste
- CSV and JSON with category and risk grade
- Risk grade on every entry for staged blocking
- Updated every day
Does Zscaler block websites? How ZIA decides
Yes, through URL Filtering rules. ZIA checks the rules in order and stops at the first match. Anything that matches no rule is allowed, so an AI agent you have not named is allowed too.
- Rule 1Approved AI tools (your own custom category)Allow
- Rule 2AI agent domains from our listBlock
- Rule 3Monitor-only AI categories in the first weeksCaution
- Rule 4+Your existing rules for other categoriesAs today
- DefaultEverything that matched nothing aboveAllowed
What the custom category needs to stop
The concern is not AI chat. It is AI that acts: it clicks, sends, buys and runs commands with the user's access. In December 2025 Gartner advised security leaders to block AI browsers for now.
AI browsers
Comet, ChatGPT Atlas, Dia and others that browse logged-in sites for the user. See blocking AI browsers.
Cloud agents
Services such as manus.im that take a task and work through websites on their own.
Extension backends
The APIs that agent extensions call. Block those and the extension stops working.
Remote MCP
Hosted MCP servers and directories such as smithery.ai that hand agents new tools.
Signs AI agents already pass through your tenant
Before you block, look. Zscaler logs every web transaction, so the first week of data usually answers "who uses what" better than a survey.
New browser installs
Downloads of AI browser installers and their update traffic from managed laptops.
Uploads to agents
Large uploads to agent platforms right after users open internal file shares or CRM exports.
OAuth sign-ins
Users signing in to agent services with their work account, which often grants mail or file access.
Developer traffic
Model API and MCP traffic from build servers and developer laptops that no one approved.
Step 1: create the custom URL category
In the classic ZIA Admin Portal this lives under Administration, URL Categories. Newer menus group it with the internet policies. Labels vary by tenant and release, so check the current admin console.
Add a category
Open URL Categories and click Add URL Category. Name it clearly, for example "AI Agent Blocklist".
Choose how entries behave
Custom URLs move the domains out of their usual category. URLs Retaining Parent Category keep them in both. For a block list, either works.
Paste the domains
Paste the plain domain list and click Add Items. In ZIA a leading dot, as in .example.com, makes an entry match subdomains too, so add the dot to each line first.
Save and activate
Click Save, then activate the pending change. Nothing applies until you activate.
Step 2: block the category with a URL Filtering rule
The category does nothing until a rule uses it. URL Filtering rules match categories, not raw URLs, which is why even one site goes into a category first.
The rule
- Open URL Filtering in the URL and Cloud App Control policy and click Add URL Filtering Rule.
- Set the Rule Order above any broader allow rules.
- Under URL Categories, select your new category.
- Leave users and locations open, or scope to a pilot group first.
- Set the action to Caution for a week, then Block.
- Save and activate.
Test it
- From a pilot device, open an AI browser's site from the list. You should see the Zscaler block page.
- Open your approved AI assistant. It should still load.
- Check the web insights logs for the rule name and the category.
- Test from home as well as the office, since ZIA follows the user.
How to block a single URL in Zscaler
Sometimes you need one AI site gone today, before the full list is in place. The method is the same, only smaller, and it takes a few minutes.
For policy reasons
- Open your AI custom category, or create one.
- Add the host with a leading dot, for example .example.com.
- Make sure a URL Filtering rule blocks that category.
- Save and activate. Test from a pilot device.
For a malicious site
- ZIA also has a global denylist in the Advanced Threat Protection policy, under Blocked Malicious URLs.
- It applies to every user and is meant for threats, not for policy choices.
- Keep AI tools you simply do not allow in a custom category instead, so you can make exceptions.
Allow approved AI tools above the block
Most companies keep at least one AI assistant and one coding agent. Put them in their own category with their own rule, so the exception is visible, owned and easy to review.
Approved AI category
- Create a second custom URL category, for example "Approved AI".
- Add only the hosts of tools you licensed, with a leading dot where subdomains are needed.
- Add a URL Filtering rule with the action Allow and give it a lower rule order number than the block rule, so it is checked first.
- Name an owner and a review date in the rule description.
Exceptions for one team
- Copy the allow rule and limit it to the group that needs the tool, such as a research team.
- Keep the block rule for everyone else.
- Set an end date and remove the rule when the project ends.
- Log each exception in your AI agent use policy register.
A rollout that does not surprise anyone
ZIA's Caution action shows users a warning page they can click through. It is a gentle first step that tells people the rule is coming and gives you log data.
Week 1: Caution
Full list with Caution. Note which groups click through most and which tools they use.
Week 2: Block high risk
Block the entries graded High and Severe. Keep the rest on Caution.
Week 3: Block AI browsers
Add AI browsers and autonomous agents to the block. Remove the apps with MDM at the same time.
Week 4: Block all
Block the full list. Approved tools keep working through the allow rule above.
Limits: will the AI list fit?
Custom URL limits are counted across all custom categories in the tenant. The AI agent list uses a small part of the default quota.
Keep the category current with the ZIA API
ZIA does not pull a custom category from a URL. Our list changes every day, so most teams run a small weekly job that adds new entries and removes retired ones through the API.
| Task | API call | Note |
|---|---|---|
| Check the quota | GET /urlCategories/urlQuota | How many custom URLs are left |
| Add new entries | PUT /urlCategories/{id}?action=ADD_TO_LIST | Send only the new domains |
| Remove retired entries | PUT /urlCategories/{id}?action=REMOVE_FROM_LIST | Send only the removed domains |
| Apply the change | POST /status/activate | Changes stay pending until activated |
How to block Google AI Mode in Zscaler
AI Mode runs on google.com, on the same search pages as normal results. Blocking the domain would block Search. There are two better routes, and they work well together.
Chrome policy
On managed Chrome, set AIModeSettings to disabled. It removes the AI Mode entry points in the address bar and the New Tab page search box.
This is the dependable control.
Custom keyword
ZIA custom categories accept keywords that match part of a URL. With SSL inspection on google.com, a keyword for the AI Mode search parameter can catch AI Mode requests.
Test carefully, since Google can change it.
Gemini app
The Gemini app has its own host, gemini.google.com, so a normal custom URL entry blocks it without touching Search.
It is a clean block.
Zscaler blocking Claude Code or GitHub Copilot?
The reverse problem is common. You approved a coding agent, and now it fails behind Zscaler. The cause is almost always SSL inspection: the tool does not trust the Zscaler certificate.
| Tool | Where it looks for the inspection certificate | Proxy settings |
|---|---|---|
| Claude Code | The operating system store with the native installer; or NODE_EXTRA_CA_CERTS pointing at a PEM file | HTTPS_PROXY, NO_PROXY |
| GitHub Copilot | The operating system store plus NODE_EXTRA_CA_CERTS | HTTPS_PROXY, or the editor's proxy setting |
| Codex CLI | CODEX_CA_CERTIFICATE, with SSL_CERT_FILE as fallback | Check the current Codex documentation |
Fix it properly
- Install the Zscaler root certificate where the tool reads it
- Or exempt the tool's documented API and sign-in domains from SSL inspection
- Keep the URL rule that allows the approved tool above the AI block rule
Never do this
- Turn off certificate checks in the tool or the editor
- Set a global "accept any certificate" option on developer machines
- Allow the whole AI list to make one tool work
MCP and agentic AI traffic through Zscaler
Searches for "Zscaler MCP security" and "Zscaler agentic AI security" often come from teams finding agents in their logs. We do not describe Zscaler's own products. Here is what a custom category can and cannot reach.
| Agent traffic | Visible to ZIA | What to do |
|---|---|---|
| Remote MCP server over HTTPS | Yes, by host name | Block with the custom category; allow approved servers above it |
| MCP directory or marketplace | Yes | Block, so new servers cannot be pulled in |
| Local MCP server on the laptop | No, it never leaves the device | MCP allowlist in each client: see MCP allowlist |
| Agent extension in the browser | Its backend, yes | Block the backend and the extension ID in browser policy |
| Cloud agent acting for the user | The user's login and uploads, yes | Block, and review OAuth grants in your identity provider |
Load the list once, update it weekly
The download includes a plain domain list to paste, a CSV and JSON for scripts, and a risk grade on every entry. The lists update every day, and we set up your download access within one business day of your order.
- Create the custom URL category and paste the list
- Add one URL Filtering rule, Caution then Block
- Activate and test from office and home
- Run the weekly add and remove job through the API
- Pair it with browser and MCP settings on devices; see AI at the firewall
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
Zscaler and AI blocking: questions
How do I block AI tools in Zscaler?
Create a custom URL category and fill it with the AI agent domains from our list, written with a leading dot so subdomains match. Then add a URL Filtering rule that selects the category with the action Block, place it above broader allow rules, save and activate.
Does Zscaler block websites?
Zscaler Internet Access blocks websites with URL Filtering rules. Rules are checked in order and match URL categories, including custom ones. Traffic that matches no rule is allowed by default.
How do I block a URL in Zscaler?
Add the URL to a custom URL category, block that category with a URL Filtering rule and activate. Rules match categories, not single URLs, so even one site goes into a category first.
How do I block Google AI Mode in Zscaler?
AI Mode runs on google.com, so blocking the domain would take Search with it. The dependable control is the Chrome policy AIModeSettings set to disabled. With SSL inspection, a custom keyword for the AI Mode parameter is an option to test carefully.
Why is Zscaler blocking Claude Code or GitHub Copilot?
Usually SSL inspection: the tool does not trust the Zscaler certificate. Install the root certificate where the tool reads it, for example the OS store or NODE_EXTRA_CA_CERTS, or exempt the tool's documented domains from inspection. Never turn certificate checks off.
How many custom URLs can a ZIA tenant hold?
By default 25,000 across all custom categories, with more available from Zscaler. An AI agent list of a few thousand domains fits easily. Check the current quota before you add other large lists.
Can Zscaler pull the AI list from a URL by itself?
Custom categories are filled in the portal or through the ZIA API, not pulled from a URL. Most teams paste the list once, then run a small weekly script that calls the API and activates the change.
Zscaler and Zscaler Internet Access are trademarks of Zscaler, Inc. Google, Chrome, Gemini and Google Admin console are trademarks of Google LLC. Microsoft and Edge are trademarks of Microsoft Corporation. GitHub and GitHub Copilot are trademarks of GitHub, Inc.
Claude and Claude Code are trademarks of Anthropic, PBC. ChatGPT, ChatGPT Atlas and Codex are trademarks of OpenAI. Perplexity and Comet are trademarks of Perplexity AI, Inc.
Dia is a trademark of The Browser Company of New York. Manus and Smithery are trademarks of their respective owners. Gartner is a trademark of Gartner, Inc.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.