AI agent identity and permissions: who is the agent acting as?
Most AI agents in your company have no identity of their own. They borrow a person's browser session, tokens or terminal and act with everything that person can reach. Before you approve any agent, know whose rights it uses and who can widen them.
Typical agent today
- Acting as
- The signed-in employee
- Can reach
- Every site and app with a saved session
- Approvals
- Set by the user in the agent
- Audit trail
- Shows the employee, not the agent
Agent you can approve
- Acting as
- Its own identity with a named owner
- Can reach
- Only the resources you granted
- Approvals
- Locked by managed settings
- Audit trail
- Shows the agent
Next step
AI Agent Blocklist
Block the agents that borrow your staff's identities, such as agent browsers, agent extensions, coding CLIs and agent platforms, and keep only the agents you have given an owner and locked settings.
From $99 a month for one organisation
Four ways an AI agent gets its identity
Every agent needs some identity to act. Ask which of these four it uses, because that decides what it can reach and who sets its limits. Only the last one shows up as itself in your logs.
AI browsers and agent extensions
The agent clicks and types inside the user's browser, with the user's cookies and saved logins.
- Reaches: every signed-in web app
- Limits set by: the user, in the agent
- You control: the browser, the extension and the network
Agent platforms and assistants
The user signs in with a work account and consents to access to mail, calendar or files.
- Reaches: whatever the granted scopes allow
- Limits set by: consent settings in your identity provider
- You control: consent rules and the network
Coding agents and CLIs
The agent runs commands as the developer, with their keys, tokens, cloud logins and environment variables.
- Reaches: repositories, secrets, sometimes production
- Limits set by: permission and sandbox settings
- You control: managed settings and installs
Agents built on your platform
The agent is registered in your identity system with its own account, an owner and scoped access.
- Reaches: only what you grant
- Limits set by: your access policies
- You control: lifecycle, access and logs
AI agent identity security: five permission layers
An agent's own permission prompts are only one layer, and usually the one the user controls. Build from the outside in. Each layer below stops what the layer under it cannot.
Claude in Chrome permissions: a guide for admins
Claude in Chrome is Anthropic's agent extension for Chrome on paid Claude plans, with the ID fcoeoabgfenejglbffodgkkbkcdhcgfn. It acts inside the user's browser, so it is a borrowed session agent with these permission settings.
| Setting | What it does | Who controls it |
|---|---|---|
| Manually approve | Asks before each action. This mode was called Ask before acting. | User, per chat |
| Automatically approve | The extension checks each action and blocks the ones it judges unsafe. | User, per chat |
| Skip all approvals | No automatic checks. This mode was called Act without asking. | User, per chat |
| Per-site prompt | On a new site: Allow this action, Always allow actions on this site, or Decline. | User |
| Approved sites list | Under Extension settings, Permissions, the user can review and revoke approved sites. | User |
| Enable for your team | Turns the extension on or off for the whole organisation. | Admin, Team and Enterprise |
| Site allowlist and blocklist | Limits Claude to approved sites, or blocks sites whatever the user allows. | Admin, Team and Enterprise |
Always asks, in every mode
- Changing permission settings
- Granting authorizations to other services
- Entering potentially sensitive information into websites
- Permanent deletions, such as emptying trash or deleting emails and files
Admin controls
- WhereOrganization settings, then Claude in Chrome, signed in as an Owner or Primary Owner
- Blocked siteA typed blocked URL shows a banner that the site is blocked by your organisation's policy, and Claude's tools stay off
- Which accountThe
forceLoginOrgUUIDpolicy limits the extension to your organisation - PlansAdmin controls exist on Team and Enterprise only, not on individual plans
Coding agents: the permission prompts users want to switch off
Searches such as "how to stop Claude Code from asking for permission" come from developers who find the prompts slow. Admins need to know which settings remove the prompts and how to lock them. Both agents below offer managed settings that users cannot override.
Claude Code
- Modes
default(shown as Manual),acceptEdits,plan,auto,dontAskandbypassPermissions - What removes promptsThe
bypassPermissionsmode, which the dangerously-skip-permissions flag also starts. Auto mode replaces prompts with a background check. - How to lock itSet
permissions.disableBypassPermissionsModeto"disable", and the same forpermissions.disableAutoModeif you want every prompt kept - Rule orderDeny rules win, then ask, then allow.
allowManagedPermissionRulesOnlymakes managed rules the only source
Codex CLI
- Sandbox modes
read-only,workspace-writeanddanger-full-access - Approval policies
on-request,neverandgranular; check the current docs, as older values are being retired - What removes promptsThe dangerously-bypass-approvals-and-sandbox flag, alias yolo, turns off both the sandbox and approvals
- How to lock itList the allowed values in
allowed_approval_policiesandallowed_sandbox_modesin requirements.toml
Claude Code managed-settings.json. Put it in /Library/Application Support/ClaudeCode/ on macOS, /etc/claude-code/ on Linux and WSL, or C:\Program Files\ClaudeCode\ on Windows.
You can also deliver it as a macOS profile for the com.anthropic.claudecode domain, as a Settings value under HKLM\SOFTWARE\Policies\ClaudeCode, or from the claude.ai admin console.
Codex requirements.toml. Put it in /etc/codex/ on macOS and Linux, or %ProgramData%\OpenAI\Codex\ on Windows.
On Macs you can deliver it through MDM in the com.openai.codex domain with the requirements_toml_base64 key, or set it under Agent security in the ChatGPT admin console.
Browser and OS permissions that hand an agent your data
Agent extensions and agent apps ask for broad permissions before they ask for anything inside the agent. These are the Chrome warnings that matter most for agents, with what each one means in practice.
Read and change all your data on all websites
The extension can read and act on every page the user opens, including signed-in apps.
Shown for all-site access and for several powerful APIsAccess the page debugger backend
The extension can drive pages the way automation tools do: click, type and read.
Permission: debuggerRead your browsing history
The extension sees every open tab and its address.
Permission: tabsCommunicate with cooperating native applications
The extension talks to a desktop app, a bridge from the browser to the computer.
Permission: nativeMessagingRead data you copy and paste
The extension can read copied text, which may include passwords and customer data.
Permission: clipboardReadScreen Recording and Accessibility
On macOS, agent apps that see and control the screen ask for these in Privacy and Security settings.
Watch for both on the same appChrome controls for extension permissions
The Chrome policy ExtensionSettings lets you limit what any extension may do, not only which extensions may install. Test each change on a small group first, because some approved extensions also use these permissions.
| ExtensionSettings field | Effect | Use it to |
|---|---|---|
installation_mode | blocked stops installs; removed also removes an installed extension | Remove named agent extensions by ID |
blocked_permissions | Extensions that request a listed permission cannot install; installed ones stop loading | Stop extensions that ask for debugger or native messaging |
runtime_blocked_hosts | Extensions cannot interact with the listed sites, up to 100 entries | Keep every extension off your bank portal and admin consoles |
runtime_allowed_hosts | Exceptions to the blocked hosts list | Let one approved extension work on one blocked site |
AI agent identity governance in six steps
Identity management for agents starts with an honest list. These steps work with the identity provider, MDM and firewall you already run.
List every agent
Record each agent, who runs it and which of the four identity types it uses. Our AI agent inventory guide shows where to look.
Name an owner
Every approved agent needs a person who answers for it, a stated purpose and a review date. No owner means no approval.
Give it its own identity
Where the platform supports it, register the agent with its own account instead of a person's. Agents built on Microsoft platforms, for example, can be registered with Microsoft Entra Agent ID.
Require admin consent
Set your identity provider so users cannot grant new apps access to mail and files on their own. Review the grants that already exist.
Lock the agent's settings
Deploy managed settings for the agents you allow: site lists for Claude in Chrome, managed settings for Claude Code, requirements for Codex.
Block everything else
Agents that cannot be identified or locked stay out. Our list covers their domains, extension IDs, app IDs and CLI packages, and it updates every day.
How the AI Agent Blocklist closes the identity gap
You cannot give an identity to an agent you do not know about. The list names the agents that borrow identities, so you can block them on the network and devices while you approve the few that earn an owner.
| Where you enforce | Setting or tool | What our file supplies |
|---|---|---|
| Firewall and DNS filter | External or custom block list | 2,600+ AI agent domains, including agent browsers, agent platforms and MCP servers |
| Chrome and Edge | ExtensionInstallBlocklist or ExtensionSettings | Extension IDs of agent extensions |
| Macs | Jamf or Intune restrictions | macOS bundle IDs and process names of AI browsers and agent apps |
| Windows | Intune or your endpoint tools | Windows package IDs and process names |
| Developer machines | Package proxy or endpoint rules | Command-line coding agents and their package names |
fcoeoabgfenejglbffodgkkbkcdhcgfn
Manus AI Browser Operator: cecngibhkljoiafhjfmcgbmikfogdiko
Codex CLI, winget: OpenAI.Codex
Codex CLI, npm: @openai/codex
A few example entries. Every entry in the full list carries the tool name, its category, the identifier type and a risk grade.
Block
- Agent browsers on managed devices
- Agent extensions with no owner
- Coding agents you have not approved
- Agent platforms that ask for mail and file access
- Unapproved MCP servers, see blocking MCP servers
Watch
- DNS lookups to agent domains
- New consent grants to agent apps
- Extensions asking for debugger or native messaging
- Apps asking for Screen Recording and Accessibility
Allow
- Agents with their own identity and an owner
- Coding agents with locked managed settings
- Claude in Chrome with an admin site allowlist, if approved
- Read-only assistants that do not act
Keep borrowed-identity agents out
Load the domains into your firewall or DNS filter and the identifiers into your browser and device policies. New agents are added every day, and after an order we set up your download access within one business day.
- Plain domain list, CSV and JSON with all columns
- Hosts file, PAC file and firewall external list format
- DNS filter import files
- Chrome and Edge extension block lists for Group Policy, Intune and the Google Admin console
- macOS and Windows identifiers for Jamf and Intune
- A risk grade on every entry, to block all agents or only the higher-risk ones
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 AI agent identity and permissions
What is AI agent identity security?
It is the practice of knowing whose identity an AI agent uses, what that identity can reach, and who can change the agent's permissions. Most agents borrow an employee's browser session, OAuth tokens or terminal, so the audit trail shows the employee.
Agent identity security means giving approved agents their own identity and blocking the agents that cannot be identified.
How do I stop Claude Code from asking for permission?
On company machines, do not remove the prompts with bypass mode. Pre-approve safe, repeated commands with allow rules in managed settings and keep deny rules for secrets.
Set permissions.disableBypassPermissionsMode to disable so the skip flag stops working. Users then see fewer prompts without losing the checks that matter.
How do I stop Codex from asking for permission?
Codex asks for approval when a command needs to leave its sandbox or reach the network. Admins should not hand out the flag that removes both the sandbox and approvals.
Instead, set the allowed approval policies and sandbox modes in requirements.toml so users can work in the workspace without prompts but cannot switch the sandbox off.
Why does Claude in Chrome keep asking for permission?
It asks per site by design. On a new site it shows a prompt with Allow this action, Always allow actions on this site and Decline. Even on approved sites it still asks before downloading files, entering sensitive information and granting authorizations.
On Team and Enterprise plans, admins can limit Claude to an allowlist of sites, which keeps prompts to the sites you approved.
What are the Claude in Chrome permission modes?
The extension offers Manually approve, which was called Ask before acting, Automatically approve, where the extension checks each action and blocks unsafe ones, and Skip all approvals, which was called Act without asking.
Some actions need explicit permission in every mode, such as granting authorizations and permanent deletions.
Is there an AI agent identity management tool from Microsoft?
Microsoft Entra Agent ID gives agents registered in Microsoft Entra their own identities, with owners, access policies and sign-in logs. It covers agents that are registered there.
An extension or command-line agent that an employee installs alone never registers, so you still need device and network rules for those.
Why does an AI agents inventory say a required permission is missing?
Inventory views in admin consoles read data through admin roles and API permissions. When the account you use lacks the role or consent the view needs, it shows a missing permission error or an empty list.
Check which role the console asks for, then sign in with an account that holds it.
Anthropic, Claude, Claude Code and Claude in Chrome are trademarks of Anthropic PBC. OpenAI, Codex, ChatGPT and ChatGPT Atlas are trademarks of OpenAI.
Microsoft, Microsoft Entra, Intune, Edge and Windows are trademarks of Microsoft Corporation. Google and Chrome are trademarks of Google LLC. Apple and macOS are trademarks of Apple Inc. Jamf is a trademark of Jamf.
Perplexity and Comet are trademarks of Perplexity AI, Inc. Manus, BrowserOS, Genspark and Fellou 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.