How to block AI browser extensions in Chrome and Edge
An AI extension can read every page a person opens, and an agent extension can click, type and submit in their logged-in sessions. Staff install them in seconds, often without anyone in IT knowing.
- Read and change all your data on all websites
- Open a side panel next to every page
- Run scripts that click, type and fill forms
- See tabs and browsing activity
Exact permissions differ per extension. Check the extension's details page before you approve anything.
Next step
AI Agent Blocklist: AI extension IDs ready for your browser policies
Chrome, Edge and Firefox IDs of AI agent and assistant extensions, each with a risk grade, in files you paste into Group Policy, Intune or the Google Admin console. Updated every day.
From $99 a month for one organisation
What AI extensions can do once they are installed
Not every AI extension carries the same risk. We see four groups in managed fleets, and they need different answers from IT.
Agent extensions
They let an AI agent operate the browser: open tabs, click buttons, fill forms and submit them inside the user's signed-in sessions.
Sidebar assistants
A chat panel that reads the current page, summarises it and answers questions. Page content, including internal pages, goes to the vendor's servers.
Meeting notetakers
They record or transcribe browser meetings and store the result with the vendor. Guests in the call may never have agreed to that.
Writing helpers
They watch what people type in mail, tickets and documents to suggest text. Drafts and replies can include customer or staff data.
Agent extensions carry the most risk. Researchers showed in 2025 that hidden text on a web page can steer a browser agent into actions the user never asked for. Our page on prompt injection in AI browsers explains how that works.
How AI extensions get onto company browsers
Most fleets have no rule for extensions at all, so the browser lets anyone add anything from the store. These are the routes we see most often.
Store install
A user adds an extension from the Chrome Web Store or Edge Add-ons with two clicks. No admin rights are needed.
Other stores in Edge
Edge can install Chrome Web Store extensions once the user turns on Allow extensions from other stores.
Profile sync
A personal browser profile with sync brings its extensions onto the work laptop the moment the user signs in.
Developer mode
Unpacked extensions load from a folder when developer mode is on. They never pass a store review.
Updates
An extension that was harmless when installed can change owner or code later. Updates arrive silently.
The update route is real. In December 2024 researchers reported that fake store emails sent to extension developers led to altered updates in dozens of legitimate extensions. Our guide are AI Chrome extensions safe covers what to check.
Who is exposed, and the signs to look for
Exposure follows the data a browser can reach. Anyone who works in web apps all day is in scope, which in most companies means almost everyone.
Most exposed roles
- Finance and payroll staff signed in to banking and ERP portals
- Support teams who read customer records all day
- Developers with cloud consoles and code hosting open
- Admins whose browser holds privileged sessions
- HR, legal and health staff handling personal data
- Students and teachers on shared school devices
Signs an AI extension is in use
- Unknown IDs in your browser extension report or inventory
- A side panel or floating AI button on internal apps
- Traffic from managed laptops to AI agent domains
- Form submissions or messages sent faster than a person types
- Meeting recordings stored outside company tools
- Users asking why an extension says it was blocked by an administrator
Three ways to block AI extensions
Chrome and Edge give admins three tools. Most organisations combine the first one with the third one, and move to the second when they are ready.
Blocklist by ID
ExtensionInstallBlocklist- You list the IDs people may not install
- Already installed copies are disabled and cannot be turned back on
- Everything else stays allowed
- Needs a list that keeps up with new AI extensions
Block all, allow some
Blocklist * plus ExtensionInstallAllowlist- A blocklist value of
*blocks every extension - Only IDs on the allowlist can be installed
- Unpacked extensions are blocked
- Needs an approval process for new requests
Fine rules per extension
ExtensionSettings- One JSON policy for install mode, permissions and sites
- Modes: allowed, blocked, force_installed, normal_installed, removed
- Can block permissions or keep extensions off chosen sites
- Overrides the older list policies
Our page on the Chrome extension allowlist walks through the strict model. If you are still deciding, read allowlist or blocklist for AI agents.
Chrome block AI extension: the steps
Pick the tool that already manages your browsers. All four routes set the same Chrome policy, so the list you load is the same.
- 1
Group Policy on domain-joined Windows
Install the Chrome ADMX templates, then open Computer Configuration > Administrative Templates > Google > Google Chrome > Extensions. Enable Configure extension installation blocklist, click Show and add one extension ID per row. Full walkthrough: block Chrome extensions with Group Policy. - 2
Registry on single machines
Under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallBlocklist create string values named 1, 2, 3 and so on, each holding one ID. A Group Policy setting for the same policy wins over a hand-made registry value. - 3
Intune on cloud-managed Windows
Create a Settings catalog profile for Windows 10 and later, search the settings picker for the blocklist setting and paste the IDs. Our guide to blocking Chrome extensions with Intune has the details. - 4
Google Admin console for managed browsers and accounts
Go to Devices > Chrome > Apps & extensions > Users & browsers, pick the organisational unit or group, find the extension and set Installation policy to Block. Chrome browser management must be on for that unit. See Chrome extensions in the Google Admin console. - 5
Check the result
Open chrome://policy on a test machine, click Reload policies and confirm ExtensionInstallBlocklist shows your entries with status OK. Then try to add a blocked extension from the store.
Macs read the same policy names from a configuration profile. Our guide to blocking Chrome extensions on Macs with Jamf shows the profile.
Example AI extension IDs from the list
Every entry in our files has the tool name, the store, the ID, a category and a risk grade. These five rows show the format. The full list is what you subscribe to.
| Extension | Store | Extension ID | Category | Risk grade |
|---|---|---|---|---|
| Manus AI Browser Operator | Chrome Web Store | cecngibhkljoiafhjfmcgbmikfogdiko | General autonomous agents | Graded |
| Sider Operator | Chrome Web Store | mokiolnliafiddobcgmmnmhbmimpccon | Browser copilots and assistants | Graded |
| HARPA AI | Chrome Web Store | eanggfilgoajaocelnaflolkadkeghjp | Browser agents and web automation | Graded |
| Nanobrowser | Chrome Web Store | imbddededgmcgfhfpcjmijokokekbkal | Browser agents and web automation | Graded |
| Claude (Claude in Chrome) | Chrome Web Store | fcoeoabgfenejglbffodgkkbkcdhcgfn | General assistants | Graded |
The same tool usually has a different ID in each store. Sider Operator in Edge Add-ons is kgkeacnfccpmbaiklacgpnlheandnlmi, not the Chrome ID above. Our Edge extension blocklist guide explains why Edge needs both sets.
Block AI extensions in Firefox and Safari
Many fleets run a second browser. The policies differ, but the idea is the same: list the AI add-ons by ID and set them to blocked.
Firefox: ExtensionSettings
- Set installation_mode to blocked for each add-on ID
- In Firefox, blocked also removes an add-on that is already installed
- The
*entry accepts only allowed or blocked - Deploy with policies.json, the Firefox Group Policy templates, or the registry key Software\Policies\Mozilla\Firefox\ExtensionSettings
- Find IDs in the Add-ons section of about:support
Safari: managed extensions
- Apple's Safari extensions management declarative configuration sets each extension to Allowed, Always On or Always Off
- Supported from iOS 18, iPadOS 18 and macOS 15 on supervised devices
- Extensions are named by a composed identifier with the developer's team ID
- A
*entry applies a state to all extensions - Not every MDM offers every key yet, so check yours
Safari extensions ship inside Mac apps. Blocking the app with your MDM often removes the extension at the same time.
What to block, what to monitor, what to allow
A blanket ban on every AI extension will meet resistance. The risk grade in our list lets you draw the line where your policy needs it.
Block
- Agent extensions that click, type or submit for the user
- Extensions graded High or Severe in our list
- AI extensions with access to all sites on admin and finance devices
- Unknown AI extensions with no approval on file
- Meeting recorders where consent rules apply
Monitor
- Moderate graded assistants that only summarise pages
- Traffic from managed devices to AI agent domains
- New IDs that appear in your extension inventory
- Extensions that change owner or permissions in an update
Allow
- AI tools your company licensed and reviewed
- Approved assistants on an allowlist for named groups
- Extensions kept off sensitive apps with runtime_blocked_hosts
- Tools that meet your AI acceptable use policy
This ExtensionSettings example removes one agent extension, stops every extension from using the debugger permission and keeps all extensions off a payroll site. Use your own host patterns and test in a small group first.
Roll out the block without a help desk rush
Blocking extensions people already use will create tickets. A short, planned rollout keeps them few and keeps the exceptions visible.
Take stock
Pull the extension inventory from your browser management or endpoint tool. Match the IDs against the AI list and note which AI extensions are in use, on how many devices and in which teams.
Decide the line
Agree with security and the business which grades you block outright and which tools you approve. Write the decision into your AI use policy so the help desk can point to it.
Tell people first
Send a short note: which extensions stop working, why, and how to request an approved tool. Users who hear it first raise far fewer tickets than users who find a greyed out icon.
Test group, then everyone
Apply the blocklist to IT staff and a few volunteers. Check chrome://policy and edge://policy, then widen the assignment to all managed browsers.
Keep the list current
Replace the policy list with each new file. New AI extensions are blocked before most users find them, and nobody has to search the stores by hand.
Close the side doors
A blocklist covers store installs by ID. These Chrome policies close the routes around it. Edge has matching policies for most of them.
ExtensionDeveloperModeSettings
Set to 1 (Disallow) so users cannot turn on developer mode and load unpacked extensions. Available from Chrome 128.
ExtensionInstallTypeBlocklist
The value command_line stops extensions loaded with a command line switch. Available from Chrome 120.
ExtensionUnpublishedAvailability
Set to 1 to disable extensions that were taken down from the Chrome Web Store. Available from Chrome 115.
BlockExternalExtensions
Stops external extensions, the kind other software drops onto the machine, from being installed.
ExtensionAllowedTypes
Limits types to extension, theme, user_script, hosted_app, legacy_packaged_app or platform_app. Leave out types you do not use.
Browser sign-in and sync
Personal profiles bring their own extensions. Decide whether personal accounts may sign in to managed browsers at all.
Extension policies do not touch AI built into the browser itself, or separate AI browsers. Use the Gemini in Chrome policies for Chrome's own AI, and block AI browsers as apps and domains.
The AI Agent Blocklist
Stop chasing new AI extensions by hand
New AI agent extensions appear every week, often under names that do not say AI. We add them to the list as they appear, with a risk grade, so your policy keeps up without anyone searching the store.
- Chrome, Edge and Firefox extension IDs of AI agent and assistant extensions
- Policy files for Group Policy, Intune and the Google Admin console
- 2,600+ AI agent domains for your firewall or DNS filter
- Risk grade per entry, so you can block all or only the higher-risk ones
- CSV and JSON with every column, 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
Questions about blocking AI extensions
How do I block AI extensions in Chrome for everyone?
Put the extension IDs into the ExtensionInstallBlocklist policy (Group Policy name: Configure extension installation blocklist) or set each ID to blocked in the Google Admin console under Devices > Chrome > Apps & extensions > Users & browsers.
For a stricter setup, block everything with * and allow only approved IDs.
Does blocking remove an AI extension that is already installed?
In Chrome and Edge a blocklisted extension that is already installed is disabled and the user cannot turn it back on. It is not uninstalled.
If you need it gone, Chrome's ExtensionSettings policy has an installation_mode of removed. In Firefox, the blocked mode removes an installed extension.
How do I block the Manus AI extension in Chrome?
Add the Chrome Web Store ID of Manus AI Browser Operator, cecngibhkljoiafhjfmcgbmikfogdiko, to your extension blocklist through Group Policy, the registry, Intune or the Google Admin console.
Block the manus.im domain at your firewall or DNS filter as well, so the web app is covered too. More on the agent itself in our Manus AI security page.
Can I block AI extensions in Firefox?
Yes. Firefox's ExtensionSettings policy accepts an installation_mode of blocked for each add-on ID, or for * to block all add-ons.
Set it in policies.json, through the Firefox Group Policy templates, or in the registry under Software\Policies\Mozilla\Firefox\ExtensionSettings.
Can I block AI extensions in Safari?
On supervised devices with iOS 18, iPadOS 18 or macOS 15 and later, Apple's Safari extensions management declarative configuration lets an MDM set each extension to Allowed, Always On or Always Off.
Check whether your MDM supports it. On a Mac, removing the app that ships the extension is often simpler.
What about extensions to block AI Overviews and AI summaries?
Those are consumer extensions that hide AI answers on search pages. They do a different job: they change what one person sees, they do not stop AI tools from reading company pages or acting for the user.
For a managed fleet, use browser policies instead. Our page on Chrome AI policies in the Google Admin console lists them.
How do I disable Google's own AI features in Chrome?
Gemini in Chrome and Chrome's other generative AI features are not extensions, so the extension blocklist does not touch them.
They have their own Chrome policies, which you set in the Google Admin console, Group Policy or Intune.
Google, Google Chrome, Chrome Web Store and Gemini are trademarks of Google LLC. Microsoft, Microsoft Edge and Microsoft Intune are trademarks of Microsoft Corporation. Firefox is a trademark of the Mozilla Foundation.
Apple, Safari, Mac, macOS, iOS and iPadOS are trademarks of Apple Inc. Jamf is a trademark of JAMF Software, LLC.
Claude is a trademark of Anthropic PBC. Manus, HARPA AI, Sider, Nanobrowser and Lunabot 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.