Chrome extension allowlist

Chrome extension allowlist: allow only the extensions you approved

With an open Chrome Web Store, anyone can add an AI agent extension in two clicks. An allowlist turns the default around: nothing installs unless IT approved its ID, and you decide which AI tools make the cut.

ExtensionInstallBlocklist*
+
ExtensionInstallAllowlistapproved IDs only
Resultonly approved extensions run

Next step

AI Agent Blocklist: check every allowlist request against a daily list of AI agent extensions

Chrome, Edge and Firefox IDs of AI agent and assistant extensions with a risk grade, so an AI agent never slips onto your allowlist by accident.

From $99 a month for one organisation

Why an open extension store is the problem

Chrome lets users add extensions without admin rights. That was a small risk when extensions changed colours and blocked ads. AI extensions read pages and send them out, and agent extensions act in the user's signed-in sessions.

Two clicks

That is all it takes to install an extension from the store on an unmanaged Chrome profile.

No admin rights

Store installs run in the user's profile, so local admin restrictions do not stop them.

All sites

The access many AI extensions request, which covers internal apps, mail, HR and finance portals.

A blocklist only stops the extensions you already know about, and new AI agent extensions appear every week, many with names that do not mention AI.

An allowlist stops the unknown ones too, which is why regulated teams and schools prefer it. Our allowlist or blocklist guide compares both.

How the Chrome extension install allow list works

The allowlist is not a separate switch. It is a list of exceptions to the blocklist, so it only does something once the blocklist blocks. This is how Chrome decides when someone tries to install an extension.

Is the ID on ExtensionInstallForcelist?
yes: installed silently and locked, the blocklist does not apply
no: is the blocklist set to * or does it list this ID?
no: install allowed
yes: is the ID on ExtensionInstallAllowlist?
Yes: install allowed if the extension is packed and signed
No: blocked, with your custom message if you set one
  • * means block everything

    A blocklist value of * blocks all extensions by default. Only IDs on the allowlist are exempt.

  • Unpacked extensions stay blocked

    With *, allowlisted extensions are allowed only if they are packed and signed. Unpacked folders loaded in developer mode are blocked.

  • Installed extensions are disabled

    Extensions already on the machine that are not on the allowlist are disabled, and the user cannot turn them back on. Taking an ID off the blocklist enables it again.

  • The force list wins

    ExtensionInstallForcelist supersedes the blocklist. Everything you force install is allowed, so review that list as carefully as the allowlist.

  • ExtensionSettings overrides both

    The ExtensionSettings policy supersedes the older list policies. A per-ID entry inherits only installation_mode and update_url from its * defaults.

Build your first allowlist from what people already use

Switching on * without a list breaks every extension at once. Start from the extensions that are already installed and keep the first list short.

  1. 1

    Export the inventory

    Pull installed extensions per device from your browser management, endpoint tool or the Admin console app report. Sort by the number of devices.

  2. 2

    Take out the AI agents

    Match every ID against the AI Agent Blocklist file. AI agent and assistant extensions go to review, not straight onto the allowlist.

  3. 3

    Approve the core set

    Password manager, single sign-on helper, conferencing add-ons and the tools IT deploys. Each gets an owner and a reason.

  4. 4

    Announce, then enforce

    Tell people what changes and how to request a tool. Turn on * for a test group, read the tickets for a week, then widen it.

Three ways to set a Google Chrome extension allow list

Use the console that already manages your browsers. The result is the same policy on the device, so the IDs you approve and the AI IDs you keep out do not change.

Google Admin console

Managed browsers and accounts
  1. Open Devices > Chrome > Apps & extensions and choose User app settings (Chrome Enterprise Core: Chrome browser > Apps & extensions > Settings).
  2. Select the organisational unit and open Allow/block mode.
  3. For Chrome Web Store choose Block all apps, admin manages allowlist, or the variant where users may request extensions.
  4. Under Users & browsers, add each approved extension and allow it for that unit or group.
Apps multiplied by groups is limited to 500. Details: Chrome extensions in the Google Admin console.

Group Policy

Domain-joined Windows
  1. Add the Chrome ADMX templates to your central store.
  2. Open Administrative Templates > Google > Google Chrome > Extensions.
  3. Enable Configure extension installation blocklist and enter * as the only value.
  4. Enable Configure extension installation allow list and add one approved ID per row.
Step by step with screenshots of the settings: Chrome extensions in Group Policy.

ExtensionSettings

One JSON policy, any channel
  1. Use the policy shown in Group Policy as Extension management settings.
  2. Set the * entry to installation_mode blocked and add a blocked_install_message.
  3. Add each approved ID with installation_mode allowed.
  4. Optionally add runtime_blocked_hosts to keep approved tools off sensitive apps.
A good fit when you also block permissions or hosts. Edge reads the same structure.
{ "*": {"installation_mode": "blocked", "blocked_install_message": "Request extensions through the IT portal."}, "fcoeoabgfenejglbffodgkkbkcdhcgfn": {"installation_mode": "allowed", "runtime_blocked_hosts": ["*://*.payroll.yourcompany.example"]} }

This ExtensionSettings example blocks every extension, shows users where to ask, and allows only the Claude extension while keeping it off a payroll site. Put this in a policy that covers the approved group only.

Chrome extension allow list in the registry

On Windows machines that are not joined to a domain, you can write the same policies straight into the registry. Each list is a subkey with string values named 1, 2, 3 and so on.

allowlist.reg
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist] "1"="*" [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallAllowlist] "1"="fcoeoabgfenejglbffodgkkbkcdhcgfn" "2"="your_approved_extension_id"

Before you import

  • Replace the second value with a real ID from your approved list
  • Number the values without gaps, one ID per value
  • If Group Policy sets the same policy, Group Policy wins, so set those entries to Not Configured
  • Policies that are not configured do not appear in the registry at all
  • Open chrome://policy and click Reload policies to see the result
  • Back up the key first, because a stray * locks every user out of every extension

Running Intune? Create a Settings catalog profile for Windows 10 and later and search for the two Chrome settings above, as our Intune guide for Chrome extensions shows.

Macs take the same keys in a configuration profile, shown in our Jamf guide.

Claude in Chrome allowlist: approve it for one group, not for everyone

Many teams want to approve one AI assistant and keep the rest out. Claude in Chrome is a common request. There are two layers to set: who may install the extension, and which sites it may act on once installed.

Layer 1: who gets the extension

  • Keep * on the blocklist for the whole organisation
  • Add the Claude extension ID fcoeoabgfenejglbffodgkkbkcdhcgfn to the allowlist only in the policy or organisational unit for approved staff
  • In the Google Admin console, allow it in a group or child unit, not at the top level
  • In Group Policy or Intune, put the allowlist entry in a separate policy assigned to the approved group
  • Block the claude.ai domain for groups that must not use it at all, at your firewall or DNS filter

Layer 2: which sites Claude may act on

  • Anthropic documents site allowlists and blocklists for Team and Enterprise admins
  • An allowlist limits Claude to approved sites; a blocklist keeps it off chosen sites whatever users approve
  • Users choose how much Claude does on its own, and some actions always ask, such as permanent deletions and entering sensitive information
  • Check the current Claude admin settings for what your plan lets you enforce
Manually approveAutomatically approveSkip all approvals

Layer 2 is set inside the vendor's admin settings and only covers managed accounts. If a user signs in with a personal account, your Chrome policy is the control that still applies. Our page on blocking Claude in Chrome covers the full block for groups that should not have it.

What an extension allowlist does not stop

An allowlist is a strong control for one route. AI agents reach users through several other routes, and each needs its own rule.

AI browsers

Comet, ChatGPT Atlas and other AI browsers are separate apps with their own extension stores and policies. Block them as apps and domains: see blocking AI browsers.

AI built into Chrome

Gemini in Chrome is part of the browser, not an extension. It has its own policies, covered in disabling Gemini in Chrome.

Agents in a browser tab

Web-based agents run as normal websites. No extension policy sees them. Block their domains at the firewall or DNS filter.

Other browsers

Edge, Firefox and Safari read their own policies. A Chrome allowlist does nothing for them. Edge needs both Edge Add-ons and Chrome Web Store IDs: see our Edge extension blocklist guide.

Changes inside approved extensions

An approved extension can add agent features or change owner in a later update. Set ExtensionUnpublishedAvailability to 1 to disable extensions taken down from the store, and review approvals on a schedule.

Your own force list

Force-installed extensions bypass the blocklist. If someone adds an AI extension to the force list, the allowlist will not catch it.

An approval process that keeps AI agents out

The allowlist is only as good as the decisions that go into it. A short, repeatable review keeps it small and keeps agent extensions off it.

Request

Users ask through the Admin console request flow or a ticket, with the extension's store link and a business reason.

Match

Look up the ID in the AI Agent Blocklist file. A match tells you it is an AI tool, its category and its risk grade.

Review

Check permissions, publisher and what data it sends out. Read our checklist on whether AI Chrome extensions are safe.

Approve narrowly

Allow it for the group that asked, with runtime_blocked_hosts for payroll, HR and admin portals.

Re-check

Compare the allowlist with each new file. An ID that turns up later as an agent goes back to review.

Risk grade in our listTypical extensionSuggested decision
LowNarrow helpers that touch few sitesApprove when there is a business need and a named owner
ModerateSidebar assistants that read the current pageApprove for named groups only, keep them off sensitive hosts
ElevatedAssistants with wide access or agent modes, and meeting recordersSecurity review first, with a written exception if approved
High or SevereAgent extensions that operate the browser, such as Manus AI Browser Operator (cecngibhkljoiafhjfmcgbmikfogdiko)Decline, and block the vendor's domains as well

Chrome app deprecation and the allowlist

Admins who search for a Chrome app deprecation allowlist usually have an old Chrome App that stopped working. That is a different issue from extensions.

Chrome Apps are deprecated on Windows, macOS and Linux. Google offered a temporary policy, Extend support for Chrome Apps on Microsoft Windows, macOS, and Linux, which applied to Chrome 104 to 113 and is itself deprecated.

Adding a Chrome App's ID to the extension allowlist does not bring it back. Plan a move to a web app or a supported extension, and check chrome://policy for policy errors on the affected machines.

On ChromeOS, Google is ending Chrome App support in stages. Kiosk apps can run for a limited time through the device setting Chrome Apps allowed for kiosk mode. Check Google's current end of support schedule before you plan around a date.

Keep the allowlist healthy

  • Every allowlisted ID has a named owner and a reason
  • The list is reviewed against each new AI agent file
  • Approvals are scoped to groups, not to the whole company
  • Developer mode is off with ExtensionDeveloperModeSettings set to 1
  • Removed or unpublished extensions are disabled
  • Users see a blocked_install_message that tells them how to ask
  • Edge and Firefox have matching rules
  • The force list is reviewed as carefully as the allowlist

The AI Agent Blocklist

Know which requests are AI agents before you approve them

Your allowlist decides what runs. Our list tells you which extension IDs are AI agents and assistants, how risky each one is, and which new ones appeared since your last review. It also gives you the block files for every browser and network layer around the allowlist.

  • 5,300+ agent identifiers, including Chrome, Edge and Firefox extension IDs
  • Tool name, category, identifier type and risk grade for every entry
  • Policy files for Group Policy, Intune and the Google Admin console
  • 2,600+ AI agent domains for firewalls and DNS filters
  • CSV and JSON with all columns, updated every day
  • Download access set up within one business day of your 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.

Chrome extension allowlist questions

How do I add an extension to the Chrome allowlist?

Find the 32-character extension ID on the Chrome Web Store page or on chrome://extensions, then add it to the ExtensionInstallAllowlist policy (Group Policy name: Configure extension installation allow list), or allow it for the right organisational unit in the Google Admin console.

The allowlist only has an effect when the blocklist blocks extensions, usually with *.

Where is the Chrome extension allow list in the registry?

Machine policy lives under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. The allowlist is the subkey ExtensionInstallAllowlist with string values named 1, 2, 3 and so on, one extension ID each.

Pair it with the subkey ExtensionInstallBlocklist holding * in value 1.

How do I set an Intune Chrome extension allow list?

Create a Settings catalog profile for Windows 10 and later, search the settings picker for the Chrome allow list and blocklist settings, set the blocklist to * and add your approved IDs to the allow list.

Assign it to a test group, check chrome://policy, then widen the assignment.

Can I allowlist Claude in Chrome for some users only?

Yes. Keep * on the blocklist for everyone and add the Claude extension ID fcoeoabgfenejglbffodgkkbkcdhcgfn to the allowlist only in the policy, organisational unit or group that covers the approved users.

Does Claude in Chrome have its own allowlist of sites?

Anthropic documents site allowlists and blocklists for Team and Enterprise admins: an allowlist limits Claude to approved sites and a blocklist keeps it off chosen sites whatever users approve.

Check the current Claude admin settings for where they sit in your plan.

What is the Chrome app deprecation and does the allowlist help?

Chrome Apps are deprecated on Windows, macOS and Linux. A temporary policy, Extend support for Chrome Apps on Microsoft Windows, macOS, and Linux, applied to Chrome 104 to 113 and is itself deprecated.

An extension allowlist entry does not bring a deprecated Chrome App back; move to a web app or a supported extension. On ChromeOS, kiosk apps can run for a limited time through the device setting Chrome Apps allowed for kiosk mode.

Do allowlisted extensions still need review?

Yes. An approved extension can change owner, permissions or code in a later update, and some extensions add AI agent features over time.

Review the allowlist on a schedule and whenever a listed ID appears in an AI agent list.

Google, Google Chrome, Chrome Web Store and Gemini are trademarks of Google LLC. Microsoft, Windows, Microsoft Edge and Microsoft Intune are trademarks of Microsoft Corporation. Firefox is a trademark of the Mozilla Foundation.

Apple, Safari, Mac and macOS are trademarks of Apple Inc. Jamf is a trademark of JAMF Software, LLC. Claude is a trademark of Anthropic PBC.

Perplexity and Comet are trademarks of Perplexity AI, Inc. ChatGPT and ChatGPT Atlas are trademarks of OpenAI. Manus is a trademark of its owner.

Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.