Jamf Pro guide for Macs

Block Chrome extensions on Macs with Jamf

Mac users add AI agent extensions to Chrome as easily as anyone else, and those agents then act inside every signed-in tab. One Jamf Pro configuration profile stops them on every managed Mac. Here is how to build it and keep it current.

GeneralApplication & Custom SettingsScope
Upload
com.google.Chrome
ExtensionInstallBlocklist
imbddededgmcgfhfpcjmijokokekbkal

Next step

AI Agent Blocklist: AI extension IDs and Mac app identifiers for Jamf

Chrome and Edge extension IDs of AI agents plus macOS bundle IDs of AI browsers and agent apps, graded by risk and updated every day.

From $99 a month for one organisation

Why Macs need their own extension policy

Many organisations lock Chrome down on Windows with Group Policy and forget the Macs. Yet Macs often belong to the people with the widest access: leadership, designers with client files, developers with cloud consoles open all day.

Extensions in Chrome

AI sidebars and agent extensions installed into a Chrome profile. Controlled by Chrome policy in the com.google.Chrome domain.

Configuration profile
Extensions in Edge

The same tools from the Edge Add-ons store or the Chrome Web Store. Edge reads its own domain, com.microsoft.Edge.

Second Upload entry
AI browsers and agent apps

Separate apps such as ChatGPT Atlas or Comet. Browser policy cannot reach them, so they need app-level controls.

Restricted Software

Standard Mac accounts can still install Chrome extensions. Removing admin rights does not help here.

Agents act inside signed-in sessions, so their actions look like the user's own clicks.

Extensions update in the background and can gain new features or permissions later.

Researchers showed in 2025 that hidden text on web pages can steer AI agents that read them.

Signs AI extensions are already on your Macs

  • Chat side panels open next to webmail or the CRM
  • Extensions with access to all sites at chrome://extensions
  • Traffic from Macs to AI agent services in firewall or DNS logs
  • AI browser apps in the Applications folder of managed Macs
  • Staff asking why an assistant "logged in by itself"

Macs that need the block first

  • Finance and payroll, with banking portals open
  • Leadership and assistants with full mailbox access
  • Developers signed in to cloud consoles and code hosting
  • HR and recruiting with personal data in web apps
  • Shared and kiosk Macs where anyone can sign in to Chrome

What Chrome on a Mac reads from Jamf

Chrome on macOS takes its policies from managed preferences in the com.google.Chrome domain. A Jamf configuration profile delivers exactly that. The policy names are the same as on Windows; only the format changes from registry values to plist keys.

Plist keyTypeWhat it doesTypical value
ExtensionInstallBlocklistArray of stringsBlocks the listed extension IDs. Installed copies are disabled.AI agent extension IDs, or a single *
ExtensionInstallAllowlistArray of stringsExempts IDs from the blocklist.Approved extensions, when the blocklist is *
ExtensionSettingsDictionaryOne policy for modes, messages and permission limits. Overrides the two lists when they conflict.Per-ID entries plus a "*" default
ExtensionDeveloperModeSettingsIntegerControls developer mode on the extensions page. 1 means users cannot switch it on.1, on Chrome 128 and later
<?xml version="1.0" encoding="UTF-8"?> <plist version="1.0"> <dict> <key>ExtensionInstallBlocklist</key> <array> <string>imbddededgmcgfhfpcjmijokokekbkal</string> <string>eanggfilgoajaocelnaflolkadkeghjp</string> <string>cecngibhkljoiafhjfmcgbmikfogdiko</string> </array> <key>ExtensionDeveloperModeSettings</key> <integer>1</integer> </dict> </plist>

Example entries: Nanobrowser, HARPA AI and the Manus browser operator extension. Save the file as com.google.Chrome.plist. If Jamf reports a format error, convert it with plutil -convert xml1 and upload again.

Jamf Pro is an MDM, so managed Macs also meet Chrome's condition for force-installing an extension from outside the Chrome Web Store. That matters if you ship your own approved extension to every Mac alongside the block.

Build the Jamf Pro configuration profile

The Application & Custom Settings payload is the place for apps that read preferences from a plist, which is how Chrome works on a Mac. Jamf's own docs describe three panes; you need the Upload pane.

Create the profile

In Jamf Pro select Computers, then Configuration Profiles, then New.

Set General

Name it, for example "Chrome: AI extension blocklist". Choose computer level so every user on the Mac gets it, and Install Automatically as the distribution method.

Add the payload

Select Application & Custom Settings, open the Upload pane and click Add.

Domain and file

Enter com.google.Chrome in Preference Domain, click Upload and choose your plist. Jamf shows the keys it read.

Scope a pilot

Open the Scope tab and target a small group of test Macs first. Add exclusions for any Mac that must stay open.

Save and confirm

Click Save. Scoped Macs get the profile the next time they contact Jamf Pro. Check one before you widen the scope.

The External Applications pane offers a Jamf Repository source with forms for common third-party apps. If your Jamf Pro version lists Google Chrome there, you can use the form instead of a file. The Upload pane works in every case.

Jamf notes that user level profiles may not apply until the user logs out and back in, or the Mac restarts. For a security block, computer level is the safer choice.

Block all extensions on a Mac, allow a few

For kiosks, shared Macs and high risk teams, a strict allowlist is often right. The blocklist holds a single asterisk and the allow list names the approved IDs. Our Chrome extension allowlist guide covers how to collect and maintain that list.

Strict mode keys

  • ExtensionInstallBlocklist: one string, *
  • ExtensionInstallAllowlist: approved extension IDs
  • ExtensionDeveloperModeSettings: 1
  • Unpacked extensions stay blocked even if listed

Before you switch it on

  • List extensions on a few Macs per team at chrome://extensions
  • Keep the password manager and sign-in helpers
  • Name an owner for every approved extension
  • Publish how staff ask for an exception
<key>ExtensionSettings</key> <dict> <key>*</key> <dict> <key>blocked_install_message</key> <string>Extensions need IT approval. Use the request form on the intranet.</string> </dict> <key>cecngibhkljoiafhjfmcgbmikfogdiko</key> <dict> <key>installation_mode</key> <string>removed</string> </dict> </dict>

The same ExtensionSettings policy as a plist dictionary. The removed mode blocks the extension and takes existing copies out of Chrome; the message is added to the Chrome Web Store error, up to 1,000 characters.

Do the same for Microsoft Edge on Macs

If Edge is installed on your Macs, a Chrome-only profile just moves the problem one icon to the right. Microsoft's guidance for Jamf is to upload the Edge plist as a custom settings payload, which fits into the same profile.

Since early versions, every Edge channel on macOS reads the same com.microsoft.Edge domain, so one entry covers Stable, Beta and Dev.

Chrome entry

  • Preference Domain: com.google.Chrome
  • Keys: ExtensionInstallBlocklist, ExtensionInstallAllowlist, ExtensionSettings
  • Chrome Web Store IDs
  • Check in chrome://policy

Edge entry

  • Preference Domain: com.microsoft.Edge, case sensitive
  • Same key names as Chrome
  • Edge Add-ons IDs, plus Chrome IDs for store crossovers
  • Check in edge://policy
<key>ExtensionInstallBlocklist</key> <array> <string>ajdioenfpgabnjlclgckbbnjjhdnjkhn</string> <string>imbddededgmcgfhfpcjmijokokekbkal</string> </array>

Nanobrowser has a different ID in the Edge Add-ons store than in the Chrome Web Store, so the Edge entry blocks both. The full Edge map is on our Edge extension blocklist page.

AI browsers are apps, not extensions

In December 2025 Gartner published "Cybersecurity Must Block AI Browsers for Now". A Chrome policy does nothing against those browsers, because they are separate Mac apps with their own engines and settings.

ChatGPT AtlasAI browser
Bundle ID
com.openai.atlas
Process name
ChatGPT Atlas
More
How to block ChatGPT Atlas
CometAI browser
Bundle ID
ai.perplexity.comet
Process name
Comet
More
How to block Perplexity Comet
Record per app

Jamf Pro Restricted Software uses one record for each app you want to restrict.

Quit the process

When a scoped user opens the app, Jamf can stop the process.

Delete the app

The record can also remove the application from the Mac.

Tell the user

Show a message with the reason, and email IT about each violation.

Restricted Software matches process names, and Jamf has a guide for finding them. Use the bundle IDs to find the apps in inventory and smart groups. For a cleanup plan, see how to remove AI browsers.

Quitting the app does not stop the same agent service in an ordinary browser tab. Pair app controls with a block on the agent domains in your DNS filter or firewall.

Confirm the block on a test Mac

Use one Mac that had AI extensions installed before the profile and one clean Mac. The checks take a few minutes.

  • System Settings > General > Device Management lists your profile
  • The profile shows the com.google.Chrome settings
  • chrome://policy, Reload policies: ExtensionInstallBlocklist has status OK
  • The value list matches your uploaded plist
  • Installed agent extensions are disabled and cannot be switched on
  • The Chrome Web Store refuses to add a blocked extension
  • Approved extensions keep working
  • edge://policy shows the Edge entry on Macs with Edge
  • Opening a restricted AI browser triggers your Restricted Software action
  • The Jamf Pro logs for the profile show it completed

If chrome://policy shows nothing, check the domain spelling first. com.google.chrome in lower case is a different domain, and Chrome will not read it.

Scope the profile in stages

A Chrome extension block touches everyone who opens a browser. Rolling it out in rings gives you time to fix the allow list before the whole company notices.

RingScope targetWhat you look forMove on when
IT MacsA static group with IT staff MacsProfile installs, chrome://policy shows OK, nothing breaksTwo working days without surprises
One teamA group for one department that uses many AI helpersException requests, missing approved extensionsThe allow list is stable
High risk rolesGroups for finance, HR, leadership and adminsBlocked agent extensions are disabled on every MacEvery Mac in the group reports the profile
EveryoneAll managed computers, with exclusions for documented exceptionsHelp desk volume and new exception requestsThe profile is part of your baseline

Keep the IT ring in scope for good. Every later change to the plist reaches those Macs first, so you see problems before your users do.

Common mistakes with Chrome profiles in Jamf

When a Chrome policy does not apply on a Mac, the cause is usually small. These are the ones we see most often.

Wrong preference domain

The domain must be com.google.Chrome with a capital C. A lower case domain creates a valid profile that Chrome never reads.

The list typed as one string

ExtensionInstallBlocklist is an array of strings. A single string with commas in it is not a list, so Chrome reports an error for the policy.

Two profiles for the same domain

If two profiles both deliver com.google.Chrome settings to one Mac, you cannot rely on which values win. Keep one profile that owns the Chrome domain.

User level instead of computer level

User level profiles may wait for the next login. Other accounts on the same Mac stay unprotected. Use computer level for a security block.

ExtensionSettings and the lists disagree

When both are set, ExtensionSettings wins for any extension it names. Put each extension in one place, or make both say the same thing.

A binary plist

Plists saved by some tools are binary. Convert the file with plutil to XML before you upload it, so Jamf can read and show the keys.

Keep the Jamf profile current

A list typed in once is out of date within weeks. New agent extensions appear, and existing ones publish new versions under new names.

Daily list

Our list updates every day with new AI agent extensions, their category and risk grade.

Weekly edit

Rebuild the com.google.Chrome plist from the current file and upload it to the same profile.

Confirm

Check the profile logs in Jamf Pro and chrome://policy on one IT Mac before you close the change.

Keep each uploaded plist with your change record. When someone asks which extensions were blocked on a given day, you can answer in a minute.

What to block, what to watch, what to allow

Every entry in our list has a category and a risk grade. You can block all AI agent extensions at once or start with the higher risk grades.

Block

  • Browser agent and operator extensions
  • Extensions of general autonomous agents
  • AI browsers on Macs that handle client data
  • Unknown AI extensions asking for all sites

Watch

  • Reading and summary sidebars
  • Meeting note helpers
  • Writing assistants in webmail
  • AI domains in your firewall or DNS logs

Allow

  • The AI assistant your company licensed, such as Claude in Chrome when approved
  • Password managers and sign-in helpers
  • Your own extensions
  • Each with an owner and a review date

One list for every Mac, updated daily

New AI agent extensions and AI browsers appear every week. The AI Agent Blocklist keeps the IDs current so your Jamf profile does not go stale.

  • Chrome, Edge and Firefox extension IDs of AI agent and assistant extensions
  • macOS bundle IDs and process names of AI browsers and agent apps for Jamf
  • 2,600+ AI agent domains in plain, CSV, JSON, hosts, PAC and firewall formats
  • Download access set up within one business day of your order

From $99 a month for one organisationMSP and product licences on the pricing page

See plans Ask a question

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.

Jamf and Chrome extension questions

How do I block Chrome extensions with Jamf?

In Jamf Pro go to Computers > Configuration Profiles > New, set the level to Computer, add the Application & Custom Settings payload and use the Upload pane. Enter com.google.Chrome as the preference domain and upload a plist with the ExtensionInstallBlocklist key.

Scope it to a pilot group, save, and check chrome://policy on a test Mac.

Which preference domain does Chrome use on macOS?

Google Chrome reads managed policies from the com.google.Chrome preference domain. Microsoft Edge uses com.microsoft.Edge, which is case sensitive and covers all Edge channels.

Can Jamf block all Chrome extensions except approved ones?

Yes. Put a single asterisk in the ExtensionInstallBlocklist array and list the approved extension IDs in ExtensionInstallAllowlist. Chrome then blocks every extension that is not on the allow list.

Why does chrome://policy not show my Jamf profile?

Check that the profile is installed under System Settings > General > Device Management, that the preference domain is exactly com.google.Chrome, and that the plist is valid XML. Then quit Chrome or select Reload policies.

User level profiles may only apply after the user logs out and back in.

Does the same profile block extensions in Microsoft Edge on a Mac?

No. Edge reads its own preference domain, com.microsoft.Edge. Add a second Upload entry in the same Application & Custom Settings payload with that domain and the Edge extension IDs.

Can Jamf block AI browsers such as ChatGPT Atlas or Comet?

AI browsers are separate apps, so a Chrome policy does not touch them. Jamf Pro Restricted Software can act when a listed process starts, for example by quitting it, deleting the app and showing a message. Use the app's process name and bundle ID to target it.

Windows PCs in the same fleet? Use Intune or Group Policy and the registry. Chromebooks and cloud managed Chrome use the Google Admin console.

Starting from scratch? Read how to block AI browser extensions first.

Jamf and Jamf Pro are trademarks of Jamf Software, LLC. Apple, Mac and macOS are trademarks of Apple Inc. Google, Chrome and Chrome Web Store are trademarks of Google LLC. Microsoft and Microsoft Edge are trademarks of the Microsoft group of companies.

ChatGPT and ChatGPT Atlas are trademarks of OpenAI. Perplexity and Comet are trademarks of Perplexity AI, Inc. Claude is a trademark of Anthropic, PBC. Gartner is a trademark of Gartner, Inc. Manus, HARPA AI and Nanobrowser 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.