Chrome AI Policies: Turn Off AI Mode, Gemini and Agents in Google Admin
Chrome now ships AI in the address bar, an assistant that reads the page you are on, and agent features that can click for the user. Users also add AI agent extensions on top.
Here is which Chrome policy controls which feature, where to set it, and how to block the agents Chrome's own settings do not cover.
AI Agent Blocklist for Chrome and Google Admin
Chrome extension IDs of AI agent extensions, ready for the Google Admin console and Group Policy, plus 2,600+ agent domains, updated every day.
What are Chrome policies, and where do they come from?
A Chrome policy is a setting the admin sets and the user cannot change. The same policy name works from several places. Pick the one you already use to manage browsers.
Google Admin console
Cloud policy for managed ChromeOS devices, signed-in users and enrolled browsers. Some AI defaults can only be set here.
Group Policy and registry
Chrome administrative templates on Windows, or values under the Chrome policy key in the registry.
MDM such as Intune
The Intune Settings catalog includes Chrome settings, and newer ones can come from imported templates. See Intune.
macOS profiles
Configuration profiles for the Chrome preference domain, pushed by Jamf, Kandji, Mosyle or another MDM.
On any client, open chrome://policy to see every policy that applies, its value and its source. Use it after each change; it is the fastest way to find a typo or a conflict.
The problem: AI is now in several parts of Chrome
Each AI surface sends different data and has its own switch. Turning off one leaves the others on. The last two cards are not Chrome features at all, and Chrome's AI settings do not touch them.
AI Mode in the address bar
AI Mode answers from the address bar and New Tab page search box when Google is the default search engine.
Gemini in Chrome
An assistant that can use the content of the page and tabs the user is viewing, with the user's permission.
Auto browse
Agent features that let Gemini act on web pages: navigate, fill forms and complete tasks for the user.
Content sharing with AI Mode and Lens
Sharing page or file content with AI Mode and Lens from the side panel or tabs.
Writing and tab helpers
Help me write, Tab compare, AI history search, DevTools AI features and Create themes with AI.
Generative AI policy defaults
One default for the covered features you have not set one by one.
AI agent extensions
Third-party extensions such as Claude in Chrome, Manus Browser Operator or HARPA AI that read pages and click. Chrome's AI settings do not cover them.
Other AI browsers
Perplexity Comet, ChatGPT Atlas, Dia and others are separate apps. Chrome policies do not apply to them at all.
AI sites in a tab
Agent platforms and AI tools opened as websites. Policy handles them only through URL blocking.
Who is exposed, and signs to look for
The risk sits where browser sessions reach sensitive systems. An assistant that reads the open page sees whatever that page shows, and an agent that acts can do whatever the user can.
Most exposed
- Finance staff with banking, payment and ERP pages open all day.
- HR and recruiting teams working in personal data.
- Support agents inside ticket systems full of customer details.
- Admins whose browser reaches cloud and identity consoles.
- Teams under contracts or rules that limit where data may go.
Signs to look for
- chrome://policy on a sample of machines shows no Generative AI policies at all.
- Extensions with AI or agent in the name and access to all sites in your extension inventory.
- Managed browser reporting in the Admin console shows AI sites among top visited apps.
- Help desk questions about "the Gemini button" or "AI Mode" from users.
- Installers for other AI browsers in your software inventory.
Gartner's December 2025 advice, titled "Cybersecurity Must Block AI Browsers for Now", pushed many security teams to act on browser AI. Our page on Gartner's advice to block AI browsers covers what it means for policy.
Chrome AI policy reference
These are the settings that matter most for AI agents and AI data sharing. Values come from Chrome's policy definitions. New AI policies arrive often, so check the current admin console and policy list before you roll out.
| Admin console setting | Chrome policy | Values | Notes |
|---|---|---|---|
| Generative AI policy defaults | GenAiDefaultSettings | 0 allow and improve AI models 1 allow without improving models 2 do not allow | Admin console only. Applies to covered features you have not set yourself. The enterprise default is 1. |
| Google AI Mode integrations | AIModeSettings | 0 allow 1 do not allow | Address bar and New Tab page search box. Needs Google as default search. Unset follows the defaults setting. |
| Gemini integrations | GeminiSettings | 0 allow 1 do not allow | Gemini in Chrome. Also needs the Gemini app service on for the user. |
| Gemini acting on web pages | GeminiActOnWebSettings | 0 allow 1 disallow | Auto browse. No effect if Gemini integrations is off. The Admin console default is disallow. |
| Allowed and disallowed URL patterns | GeminiActOnWebAllowedForURLs GeminiActOnWebBlockedForURLs | Lists of URL patterns | Limit where Gemini may act. A URL on both lists is allowed. |
| Google AI Mode content sharing | SearchContentSharingSettings | 0 allow 1 do not allow | Sharing page or file content with AI Mode and Lens. Separate from AIModeSettings. |
| Help me write | HelpMeWriteSettings | 0 allow and improve 1 allow without improving 2 do not allow | Writing help in text fields. |
| Tab compare, History search, DevTools AI features, Create themes with AI | TabCompareSettings, HistorySearchSettings, DevToolsGenAiSettings, CreateThemesSettings | Check the current policy list | Lower risk helpers. Set them through the defaults setting or one by one. |
Generative AI policy defaults cannot be set by Group Policy or the registry. On browsers you manage only through Windows or an MDM, set each feature policy, such as AIModeSettings and GeminiSettings, one by one.
Block AI Mode and Gemini in the Google Admin console
The settings live together in one section, so the work takes minutes. Changes usually reach browsers within minutes and can take up to 24 hours.
Open Chrome settings
Sign in with an admin account that can manage Chrome settings. Go to Devices, Chrome, Settings, then Users & browsers.
Pick the scope
Select an organizational unit or a group. Group settings override organizational units, so check both if a result surprises you.
Go to Generative AI
Scroll to the Generative AI section. It lists the defaults setting and each feature setting.
Set AI Mode and Gemini
Google AI Mode integrations and Gemini integrations: choose the do not allow option for the scope.
Keep agents off
Confirm Gemini may not take action on web pages, and set the defaults setting to do not allow for anything left.
Save and verify
Save, or Override for a child unit. On a test device, open chrome://policy and reload policies.
On Chrome Enterprise Core, the path starts at Menu, then Chrome browser, then Settings. To also stop Gemini at the account level, turn the Gemini app service off for the same users. More detail in how to disable Gemini in Chrome.
Chrome: disable AI Mode with Group Policy or the registry
For Windows browsers managed through Active Directory, set the same policies with Chrome's administrative templates. Install the current templates first: older ones do not include the newest AI policies.
Group Policy
- Copy the current Chrome ADMX and ADML files to your central store.
- Open the policy under Administrative Templates, Google, Google Chrome, and find the Generative AI section.
- Set AI Mode and Gemini integration to the do not allow option, and Gemini acting on web pages to disallow.
- Link the GPO, run a policy update on a test machine and check chrome://policy.
Registry values
Machine policy for Chrome lives under one key. DWORD values:
HKLM\SOFTWARE\Policies\Google\Chrome AIModeSettings = 1 GeminiSettings = 1 GeminiActOnWebSettings = 1 SearchContentSharingSettings = 1 HelpMeWriteSettings = 2
Users who switch to another browser skip all of this. Pair Chrome policy with app controls for other browsers. See how to block AI browsers and the list of AI browsers.
Chrome policy extension settings for AI agent extensions
Agent extensions are the gap Chrome's AI settings leave open. They read every page and act on them, with the user's sessions. Block them by extension ID with ExtensionSettings or ExtensionInstallBlocklist.
Agent that navigates and acts in the browser.
Lets a general agent operate the user's browser.
Browser automation with AI models.
ExtensionSettings (one JSON policy)
{
"fcoeoabgfenejglbffodgkkbkcdhcgfn": {
"installation_mode": "blocked",
"blocked_install_message": "AI agents need IT approval"
},
"cecngibhkljoiafhjfmcgbmikfogdiko": {
"installation_mode": "blocked"
}
}
In the Google Admin console
- Go to Devices, Chrome, Apps & extensions, Users & browsers.
- Select the organizational unit.
- Add each extension by ID and set it to Block, or set a default that blocks everything not on your allowlist.
- A blocked extension is turned off where it is already installed.
Step by step: block Chrome extensions in Google Admin.
Our download includes the full Chrome and Edge extension block lists, formatted for Group Policy, Intune and the Google Admin console. For an allowlist-first approach, see the Chrome extension allowlist guide.
Block AI agent sites with URLBlocklist
Some agents run as websites: agent platforms, browser agent services and MCP hubs. URLBlocklist stops Chrome opening them on managed browsers, on and off your network.
What to put in it
- Domains of AI agent platforms you have not approved, such as manus.im or browser-use.com.
- Download pages of AI browsers, so Chrome cannot fetch the installer.
- MCP hubs if developers should only use approved servers.
Limits to know
- URLAllowlist holds up to 1,000 exceptions. Keep exceptions short.
- It only acts inside managed Chrome. Desktop agents and other browsers need DNS or device controls.
- For whole-network coverage, see DNS blocking of AI agents.
What to turn off, what to limit, what to keep
Not every AI feature carries the same risk. A sensible baseline for most companies looks like this; adjust per organizational unit.
Turn off
- Gemini acting on web pages
- AI agent extensions from other makers
- Content sharing for teams handling regulated data
- AI agent platform sites you have not approved
Limit
- Gemini in Chrome, only for groups covered by your Workspace terms
- AI Mode, per organizational unit
- Gemini acting only on allowed URL patterns, if you pilot it
Usually fine
- DevTools AI for developers who need it
- Help me write without improving models
- Tab compare and themes, if your policy allows
Check that the policies hold
A policy that is set but not applied gives false comfort. Run these checks after rollout and again after each Chrome update.
- chrome://policy on a test device shows each AI policy with the expected value and source.
- The address bar shows no AI Mode entry point for a test user in the scope.
- The Gemini button and side panel are gone for that user.
- Installing a blocked agent extension from the store shows your block message.
- A listed agent platform site shows Chrome's blocked page.
- Your device inventory shows no other AI browsers on managed machines.
Roll out in four weeks without surprising people
Turning off features people already use creates tickets and workarounds. A short, announced rollout avoids most of both.
Week 1: look
Pull your extension inventory and browser reports. List which AI features and agent extensions are in use, and by which teams.
Week 2: pilot
Apply the policies to an IT organizational unit. Fix anything that breaks, and write the one-paragraph note staff will see.
Week 3: announce
Tell staff what changes, why, which AI tools stay approved, and how to request an exception.
Week 4: enforce
Apply to all units. Block agent extensions by ID and remove other AI browsers from managed devices.
Every month: review
New AI policies appear with Chrome releases. Check the policy list and your settings after each major update.
Every day: refresh lists
New agent extensions appear daily. Load the updated extension block list so new IDs are blocked before staff find them.
Write the rules down before you enforce them. Our AI agent acceptable use policy template gives staff a clear statement of what is approved and why.
Cover what Chrome's AI settings miss
Chrome policy switches off Google's own AI. The AI Agent Blocklist covers the rest: agent extensions, AI browsers and agent sites, in files your Admin console and Group Policy accept.
- Chrome and Edge extension block lists for Group Policy, Intune and the Google Admin console
- 2,600+ AI agent domains for URLBlocklist, DNS and firewalls
- macOS and Windows identifiers of AI browsers and agent apps
- CSV and JSON with tool name, category and risk grade
- 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
Chrome AI policy questions
What are Chrome policies?
Settings an admin pushes to Chrome so users cannot change them. They come from the Google Admin console, Group Policy or the registry, macOS profiles or an MDM such as Intune. chrome://policy shows which ones apply.
Which Chrome policy disables AI Mode?
AIModeSettings set to 1. In the Google Admin console it is Google AI Mode integrations. If unset, the Generative AI policy defaults setting decides.
How do I disable AI Mode in Chrome with Group Policy?
Install the current Chrome templates, then set the AI Mode policy in the Generative AI section to the do not allow option, which writes AIModeSettings = 1. Confirm in chrome://policy.
Which Chrome policy turns off Gemini in Chrome?
GeminiSettings set to 1, shown as Gemini integrations in the Admin console. Gemini in Chrome also needs the Gemini app service on, so turning either off removes it.
How do I stop Gemini from acting on web pages?
Set GeminiActOnWebSettings to 1, or choose to disallow it in the Admin console, which is the default for managed users. URL pattern lists limit it to certain sites if you allow it.
Can one setting turn off every Chrome AI feature?
Generative AI policy defaults set to 2 turns off covered features you have not set one by one. It can only be set in the Admin console and does not cover extensions or other browsers.
Do Chrome AI policies block AI agent extensions?
No. They only control Google's built-in features. Block agent extensions by ID with ExtensionSettings or ExtensionInstallBlocklist.
Google, Chrome, Chrome Enterprise, ChromeOS, Gemini, Google Lens and Google Workspace are trademarks of Google LLC. Microsoft, Windows, Active Directory and Intune are trademarks of Microsoft Corporation. Apple and macOS are trademarks of Apple Inc.
Claude is a trademark of Anthropic PBC. Perplexity and Comet are trademarks of Perplexity AI, Inc. ChatGPT and Atlas are trademarks of OpenAI. Manus, HARPA AI, Dia, Browser Use, Jamf, Kandji and Mosyle 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.