Allowlist vs blocklist

Allowlist or Blocklist for AI Agents: Which Works?

Allow only what you approved, or block what you know is risky? With new AI browsers, agents and MCP servers arriving every week, picking the wrong model either breaks work or lets agents through.

The short answer: an allowlist where you can list everything, a blocklist where you cannot, and clear rules for which one wins.

Allowlist

  • Everything denied unless listed
  • Strong where the set is small
  • Every new tool needs a request
vs

Blocklist

  • Everything allowed unless listed
  • Works where you cannot list everything
  • Only as good as its last update
Next step

AI Agent Blocklist: the blocklist half of your AI agent policy

2,600+ AI agent domains and 5,300+ agent identifiers, each with a risk grade, updated every day, for the layers where an allowlist is not practical.

From $99 a month for one organisation

Blacklist or blocklist? The terms, briefly

People search "is it blacklist or blocklist" because both appear in older and newer documents. They mean the same thing. Blocklist and allowlist are the plainer terms now common in technical writing and product settings.

Blocklist (formerly blacklist)

A list of items that are denied. Everything not on it is allowed.

Chrome policy names: URLBlocklist, ExtensionInstallBlocklist.

Allowlist (formerly whitelist)

A list of items that are permitted. Everything not on it is denied.

Chrome policy names: URLAllowlist, ExtensionInstallAllowlist.

Why neither list works on its own

Both models fail in predictable ways when you apply them to AI agents everywhere at once. Knowing the failure tells you where each one belongs.

How an allowlist-only policy fails
  1. The web cannot be listed. An allowlist for every site staff need is a project nobody finishes.
  2. Some lists have hard limits. Chrome's URLAllowlist holds up to 1,000 exceptions.
  3. Every new tool becomes a ticket. When the queue is slow, people move work to personal devices.
  4. Broad entries creep in. One "allow all of this vendor" entry quietly covers its new agent features too.
How a blocklist-only policy fails
  1. It goes stale. A list built by hand last quarter misses the AI browsers and agents launched since.
  2. It cannot know your approvals. Without an allow layer, approved tools get blocked with the rest.
  3. An allow rule can undo it. In many tools an allow entry beats a block entry for the same name.
  4. It only covers what it sees. A domain list does nothing for an extension that is already installed.

Allowlist vs blocklist, side by side

Use this table when someone asks which model to adopt. The answer changes with what you are controlling and how well your devices are managed.

AllowlistBlocklist
Default for something newDenied until approvedAllowed until listed
A new AI agent launches todayBlocked automaticallyBlocked once the list adds it; daily updates keep that gap short
UpkeepYour team reviews every requestThe list provider tracks new agents; you manage exceptions
User frictionHigh at first, then steadyLow; people only notice listed tools
Fits wellSmall, known sets: extensions, MCP servers, commands, agent network accessLarge, open sets: web domains, DNS, unmanaged and guest devices
Typical failureGaps you cannot list, slow approvalsStale lists, broad allow rules

Which list belongs at which layer

Here is the pattern we recommend for AI agents. Allowlists where the set is small and under your control, blocklists where it is not.

LayerUseHow
Browser extensionsAllowlistBlock all by default with ExtensionSettings, allow approved IDs. Keep the agent extension list for audits and for browsers where default-deny is not possible.
Desktop apps on managed devicesAllowlist where app control is enforcedApp control or MDM rules. Elsewhere, block AI browsers and agent apps by bundle ID, package ID and process name.
Web and DNSBlocklistAgent domains in DNS filters, firewalls and URLBlocklist. Allowlists only for kiosks and locked-down segments.
MCP serversAllowlistApproved servers with pinned versions in managed agent config; MCP hubs blocked at the network.
Coding agent commands and filesBothAllow the commands a project needs, deny secrets and destructive commands in a managed settings file.
Cloud agent network accessAllowlistAgent firewalls with a short list of permitted hosts.
Built-in browser agents acting on sitesBothOff by default; if piloted, limit to allowed URL patterns and block sensitive ones.

Extensions are the easiest place to start with an allowlist. Our Chrome extension allowlist guide walks through it, and the MCP allowlist guide does the same for agent tools.

Examples: one allowlist, one blocklist

Two short policies show the difference in practice. The first denies every extension except approved ones. The second blocks named AI browsers on Windows and macOS devices that cannot run in default-deny mode.

Allowlist: Chrome extensions

ExtensionSettings with a default of blocked, and an explicit entry for each approved extension.

{
  "*": { "installation_mode": "blocked" },
  "APPROVED_EXTENSION_ID": { "installation_mode": "allowed" }
}

Agent extensions such as Claude in Chrome (fcoeoabgfenejglbffodgkkbkcdhcgfn) or HARPA AI (eanggfilgoajaocelnaflolkadkeghjp) stay blocked unless you approve them.

Blocklist: AI browser apps

On devices where you cannot deny everything, block the known AI browsers by identifier:

AppPlatformIdentifier
Perplexity CometWindowsPerplexity.Comet
ChatGPT AtlasmacOScom.openai.atlas

The full lists are in our download. See also the list of AI browsers.

Block high-risk AI agents, allow approved ones, watch the rest

Most companies land on three tiers. A blocklist with a risk grade on every entry makes the split easy: load the higher grades as blocks and treat the rest as a watch list.

Block

Higher risk grades and agents that act with user sessions.

  • AI browsers and browser agents
  • Agent extensions that click and type
  • Unapproved MCP hubs

Watch

Logged, reviewed weekly, decided per team.

  • Coding agents on developer machines
  • Meeting and research agents
  • Lower risk grades

Allow

Approved after a review, with an owner and an end date.

  • Your licensed assistant
  • Approved coding tools
  • Internal agents
Agent request or new agent seen On your allowlist? Yes: allow No: on the blocklist? Yes: block and review on request

Each request runs through our AI agent risk assessment before it moves to the allow tier.

Which rule wins when both lists match?

This is where hybrid policies break. In many tools an allow entry beats a block entry, so one broad exception silently undoes part of your blocklist. Check the order in each tool you use.

ToolWhen allow and block both matchWhat to watch
Microsoft Defender for Endpoint indicatorsAllow wins Allow, then Warn, then Block15,000 indicators per tenant. Keep allow entries narrow. See Defender.
AdGuard HomeException wins @@||name^ unblocks a name and its subdomains$important raises a rule above others, even basic exceptions.
Pi-holeAllowlist wins over subscribed blocklistsA wildcard allow entry can cover far more than intended.
Chrome URL policiesAllowlist wins URLAllowlist is the exception list to URLBlocklistUp to 1,000 exceptions.
Chrome Gemini acting on web pagesAllowed wins a URL on both lists is allowedKeep the allowed URL list short.
Coding agent managed settingsAdmin rules hold managed settings sit above user and project filesA user's own allow rule does not outrank an ask or deny rule set by the admin.

Audit allow entries as carefully as block entries. Give each one an owner, a reason and an end date, and remove it when the end date passes.

"Always allow" inside agents is an allowlist too

Searches like "copilot allow actions" come from a second kind of list: the approvals inside agent tools. Each "always allow this tool" or auto-approve click turns a one-time approval into a standing allowlist entry.

Approval prompts

Agents ask before running a command, calling a tool or acting on a page. That prompt is your last control on the device.

Auto-approve settings

Users can often switch prompts off for a tool or a whole session. Decide who may do that, and lock it in managed settings where the tool allows.

Managed settings files

Some coding agents read a managed-settings.json with allow, ask and deny rules that users cannot override. Put secrets and destructive commands under deny.

Agent firewalls

The GitHub Copilot cloud agent has a firewall under Settings, Copilot, Internet access. A recommended allowlist is on by default, custom rules can be added, and it can be disabled.

Know the scope

That firewall covers processes started through the agent's Bash tool and its built-in Playwright MCP server, not other MCP servers or setup steps.

Agents in the OS

Operating systems now ship their own agent features. See how to turn off Copilot Actions.

For one coding agent in detail, see controlling Claude Code.

robots.txt: allow or disallow AI bots is a different problem

"robots txt disallow AI bots" and "robots txt allow AI bots" are about crawlers visiting your website. That is the opposite direction from stopping your staff's agents. Both matter; they need different tools.

Your agents going out

AI browsers, agent extensions and coding agents your staff run, reaching services on the internet.

Controlled by DNS, firewalls, browser policy and MDM. This is what the AI Agent Blocklist is for.

AI crawlers coming in

Bots that visit your public website to train models or answer searches.

Asked to stay away with robots.txt. Only well-behaved crawlers follow it.

# Opt out of model training
User-agent: GPTBot
Disallow: /

User-agent: Google-Extended
Disallow: /

# Keep appearing in AI search
User-agent: OAI-SearchBot
Allow: /

GPTBot collects content that may be used for training, OAI-SearchBot is for search, and Google-Extended is a control token for Gemini training and grounding, not a separate crawler. OpenAI notes that robots.txt rules may not apply to ChatGPT-User, which acts on user requests.

Signs your current model is not working

Whichever model you run today, these symptoms tell you it needs the other half. Most teams see two or three of them within the first month of AI agent requests.

A growing request queue

An allowlist-only policy with weeks of open requests. People stop asking and start working around it.

Work moving to phones

Staff use agents on personal devices because company devices block everything new.

A list nobody updated

A blocklist last edited months ago, with none of the AI browsers launched since.

Wildcard allow entries

Entries like "everything from this vendor" that now cover its new agent features.

Agents in the logs anyway

DNS or proxy logs show agent services from devices that should not reach them.

No owner per entry

Nobody can say why an allow entry exists or when it should end.

Who owns each list

Lists without owners decay. Give every list a named owner and a review rhythm, and write both into your AI agent acceptable use policy.

ListOwnerReviewInput from
Approved AI toolsIT or security leadMonthly, and on every requestBusiness owners of each tool
Extension allowlistEndpoint or browser adminMonthlyTeams that asked for each extension
MCP server allowlistEngineering leadOn every request, with version pinsSecurity review
AI agent blocklistList provider, dailyYour exceptions monthlyDNS and proxy logs
ExceptionsWhoever approved themAt the end dateThe person who asked

How we solve it: the blocklist half, kept current

You own the allowlists, because only you know what is approved. We maintain the blocklist half for the layers where you cannot deny everything, and we keep it current so the gap for new agents stays short.

2,600+ agent domains

AI browsers, autonomous agents, agent platforms, MCP servers, coding, research, meeting, voice and sales agents.

5,300+ identifiers

Extension IDs, bundle IDs, Windows package IDs, process names and CLI packages for devices and browsers.

Risk grade per entry

Block all agents or only higher grades; use the rest as a watch list.

Updated every day

New agents are added as they appear. Every entry is checked before it enters the list.

Your tools' formats

Domain list, hosts, PAC, firewall external list, DNS filter imports, browser and device policy files.

Built to combine

CSV and JSON with tool name and category, so you can subtract your approved tools before loading.

For whole-network blocking, start with DNS or Pi-hole and AdGuard Home. For the full picture, see how to block AI agents.

Set up a hybrid policy in one week

A realistic plan for a small IT team. Each day is a few hours of work.

  1. Day 1

    List approvals

    Write down the AI tools already approved, with owners. This becomes your first allowlist.

  2. Day 2

    Extensions

    Switch browsers to default-deny for extensions with your approved IDs allowed.

  3. Day 3

    Network

    Load the agent blocklist into DNS or the firewall, minus your approved tools, in log mode first.

  4. Day 4

    Devices and MCP

    Block AI browser apps by identifier. Publish the approved MCP servers in managed config.

  5. Day 5

    Enforce and review

    Switch the network list to block, check which rule wins in each tool, and set a monthly review.

Pair your allowlists with a blocklist that keeps up

Approve what you need. Let a daily list catch the AI agents, browsers and extensions you have never heard of.

  • Plain domain list, hosts file, PAC file and firewall external list format
  • DNS filter import files
  • Chrome and Edge extension block lists for Group Policy, Intune and Google Admin
  • macOS and Windows identifiers for Jamf and Intune
  • Updated every day; access set up within one business day of an order

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

We use your details only to answer you. No newsletters.

Allowlist and blocklist questions

Should I use an allowlist or a blocklist for AI agents?

Both, at different layers. Allowlists for small, controlled sets such as extensions, MCP servers, commands and cloud agent network access. A daily blocklist for the web and DNS, where you cannot list everything you allow.

Is it blacklist or blocklist?

Both mean a list of denied items. Blocklist and allowlist are the terms now common in technical documentation and product settings, including Chrome's URLBlocklist and URLAllowlist policies.

What is the difference between blacklist and blocklist?

There is no technical difference. Blocklist is the newer, plainer term for the same idea, as allowlist is for whitelist.

How do I block only high-risk AI agents?

Use a blocklist with a risk grade on each entry. Load the higher grades into your DNS filter, firewall or browser policy, watch the rest in logs, and allow approved tools.

Does robots.txt stop AI agents?

No. robots.txt asks crawlers visiting your website to stay away, and only well-behaved ones follow it. It does nothing about agents your own staff run.

How do I allowlist MCP tools?

Keep a short list of approved MCP servers with pinned versions, enforce it in each agent's managed configuration, and block MCP hubs and unknown servers at the network.

Why does my blocklist not block an AI tool I listed?

Usually an allow rule wins. Defender indicators rank Allow over Warn over Block, and AdGuard Home exception rules unblock names. Look for a broad allow entry that covers it.

Google, Chrome and Gemini are trademarks of Google LLC. Microsoft, Windows, Edge, Intune and Microsoft Defender are trademarks of Microsoft Corporation. Apple and macOS are trademarks of Apple Inc.

OpenAI, ChatGPT and Atlas are trademarks of OpenAI. Claude and Claude Code are trademarks of Anthropic PBC. Perplexity and Comet are trademarks of Perplexity AI, Inc. GitHub and GitHub Copilot are trademarks of GitHub, Inc.

HARPA AI, AdGuard Home, Pi-hole and Jamf are trademarks of their respective owners. Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.