Home/Blog/macOS AI agent permissions: what 27.3 beta 2 tightens and what to audit now
blog

macOS AI agent permissions: what 27.3 beta 2 tightens and what to audit now

November 17, 2026 · Security News

macOS AI agent permissions preview in macOS 27.3 beta 2 covering Full Disk Access and data access controls

Apple is previewing tighter macOS AI agent permissions in macOS 27.3 beta 2, with narrower options and more transparency for Full Disk Access and the Device Control and Data Access API. The change is still in beta, with no ship date and no word on defaults. Businesses whose staff already run desktop AI agents with blanket file access should audit those grants now, because nothing in the report says the new controls will revisit approvals made before the upgrade.

Key takeaways

  • macOS 27.3 beta 2 previews finer controls over Full Disk Access and the Device Control and Data Access API.
  • Apple explicitly includes apps that run AI agents and frames the change as more transparency plus more granular choices.
  • It is a beta hardening change with no CVE attached and no confirmed release date.
  • Defaults, treatment of existing grants and MDM behavior are unconfirmed, so plan a second review when 27.3 ships.
  • Audit Full Disk Access, Screen Recording and Accessibility grants for agent apps now, including ones approved by MDM profiles.

What did Apple announce for macOS app data access?

Apple announced new macOS controls that let users decide more precisely what data an app can reach, and it named apps built on AI agents as part of the target. The Hacker News reported the change on Tuesday, November 17, 2026.

The report’s timestamp (November 17, a Tuesday) conflicts with its claim that Apple announced “on Monday.” November 16 is the likely date, but it is not confirmed.

The feature lives in macOS 27.3 beta 2, a pre-release seed for developers and testers. Apple describes the goal as more transparency plus more granular options around two existing APIs.

This is not an incident report. The source names no CVE, no CVSS score, no threat actor, no malware family and no indicators of compromise, and nobody is known to have been breached through the gap Apple is closing. It is a change to the permission model, and it shows where Apple sees desktop risk heading.

Which permissions do the new controls cover, including AI agents?

The controls cover two APIs: the Device Control and Data Access API, and Full Disk Access. Apple applies them to conventional apps and, explicitly, to apps that run AI agents on the user’s behalf.

Full Disk Access is the broadest of the two. It arrived in macOS Mojave 10.14 in 2018 under Apple’s Transparency, Consent and Control framework (TCC), and it opens protected user and app data, including what Mail and Messages store. Apple is tightening a permission model that has existed for eight years, not creating a new one.

The report names the Device Control and Data Access API but does not say which devices or data types it gates. We won’t fill that gap with guesses.

The report also quotes an Apple statement that begins “Before granting an app such” and then cuts off. We don’t have the rest. Any description of what the new prompt looks like, or which options the user picks between, would be speculation, and we won’t put a finished sentence in Apple’s mouth.

The coverage is macOS only. The report says nothing about iOS, iPadOS or Apple’s other platforms getting matching controls.

Why does broad Mac access matter once an AI agent can act?

An AI agent with Full Disk Access can read far more than the task in front of it, and it can act on what it reads without a human approving each step. That is the risk class Apple is addressing: over-privileged software on the endpoint. No documented exploit is attached to this story.

Look at how these tools get installed. An inbox assistant, a coding agent or an automation tool works poorly with narrow access, so it asks for everything. The user wants it to work, clicks Allow and moves on. Consent fatigue takes over, and the broadest grant becomes the path of least resistance. Apple’s stated aim is to give users finer choices at that moment.

Once the grant exists, two parties can steer the agent: the user, and whatever content the agent reads.

OWASP’s 2025 Top 10 for LLM applications lists prompt injection as LLM01. The indirect form hides instructions inside a document, web page or email that the agent later ingests. A permission prompt governs what software can access. It cannot distinguish an instruction typed by your employee from one hidden in a booby-trapped PDF.

The risk falls into three categories:

  • Confidentiality: documents, messages and credentials stored in files become readable in bulk.
  • Integrity: the agent can delete, move or send things with the authority it was given, at machine speed.
  • Onward exposure: if the agent sends context to a remote model, file contents leave the Mac and land with a provider you may never have vetted.

Two details trip up audits. First, Full Disk Access, Screen Recording and Accessibility are separate permissions, and a GUI-driving agent often holds all three. Review only Full Disk Access and you miss screen capture and UI control entirely.

Second, notarization is not a privilege review. Apple checks notarized software for malicious components, not for least privilege, so a signed, notarized agent can still ask for everything.

What is still unknown about macOS AI agent permissions in 27.3?

The report settles scope and intent. Nearly everything an IT manager needs for planning is still open:

  • Defaults: whether grants become stricter by default, or the prompts simply explain more.
  • Ship date: no general-availability date and no final build number for macOS 27.3.
  • Existing grants: no word on whether apps that already hold Full Disk Access get re-prompted, narrowed or left untouched after the upgrade.
  • Fleet management: nothing on whether MDM can pre-approve, defer or enforce the new prompts, or whether Privacy Preferences Policy Control (PPPC) payloads gain new keys.
  • Mechanics: prompt wording, how narrow the new options get, revocation behavior, and whether macOS logs what an agent actually accessed.
  • Motivation: which agent products drove the change, and whether Apple cited an incident or research.

Developers whose apps use either API should re-test their permission flows on beta 2 now, but nobody should write company policy around beta UI. Put a second review in the calendar for when 27.3 ships, because migration of old grants is the open question most likely to matter.

What should a business check before staff approve an AI app?

Start with the grants your Macs already hold, because nothing confirmed so far says the new controls will clean up approvals made months ago. None of the steps below needs macOS 27.3.

  1. Inventory three lists, not one. In System Settings > Privacy & Security, check Full Disk Access, Screen Recording and Accessibility separately. Flag every AI assistant, coding tool, inbox agent and automation app, and remove any grant without a documented business reason.
  2. Identify what you are actually looking at. Agent apps ship helper processes, so the name in Settings is not enough. Before revoking or upgrading, record the bundle identifier and the signing identity (replace the path with the real app):
    • mdls -name kMDItemCFBundleIdentifier /Applications/AgentApp.app
    • codesign -dvvv /Applications/AgentApp.app
  3. Check what management already approved. On a managed Mac the user toggle is not the whole story. Run these, then look for PPPC entries granting SystemPolicyAllFiles:
    • profiles status -type enrollment
    • sudo profiles show -type configuration

    An MDM profile may have pre-approved Full Disk Access that nobody on the current team remembers.

  4. Decide what may leave the device. For each agent you keep, write down whether it may send file contents to a remote model, and to which provider. If the answer is “we don’t know,” that is your finding.
  5. Default to narrow. When an app asks for Full Disk Access, ask the vendor which folders it needs. Folder-scoped access shrinks the blast radius: if injected instructions hijack the agent, it can only reach those folders.

From our engagements

When we test SMB endpoints, agent tools with Full Disk Access usually turn up on developer and executive laptops, granted during a trial and never revisited. Those same disks tend to hold API keys and passwords in plain files, which is why a secrets and credential exposure assessment pairs well with a permission review. We saw the same trust in AI tooling on dev machines in our look at a malicious Claude Code extension on Cursor.

Revoking and investigating

A grant proves capability, not misuse. If you suspect an agent was steered, revoke the grant and relaunch the app, but treat that as containment only: revocation cannot recall data already sent to a model provider.

Also, don’t weaken a suspect Mac’s protections just to read its TCC database. It is protected, and reading it on a live system may require Full Disk Access or a proper forensic image, so collect evidence first. A threat hunting and compromise assessment tells you what the agent actually touched.

Tight Mac grants cover only half the risk; how the agent handles hostile content is the other half, and that is what AI and LLM application penetration testing examines.

FAQ

Are the new macOS permission controls available now or only in beta?

Only in beta, based on the report. They appear in the macOS 27.3 beta 2 seed, and Apple has not given a general-availability date or final build number.

What is the Device Control and Data Access API on Mac?

It is one of the two APIs Apple named alongside Full Disk Access. The report does not describe which devices or data types it gates, so wait for Apple's release notes before relying on specifics.

Will existing Full Disk Access grants be revoked when macOS 27.3 ships?

Unknown. The report does not say whether existing grants are re-prompted, narrowed or left alone after upgrading, so review them yourself now and again at release.

How should businesses handle AI apps that ask for Full Disk Access?

Ask the vendor which folders the app actually needs, record its bundle identifier and signing identity, and decide in writing whether it may send file contents to a remote model.

Should I turn off every AI app on company Macs because of this release?

No. Inventory which agents hold Full Disk Access, Screen Recording or Accessibility, remove grants without a business reason, and keep the tools that pass that review.

If you’d rather have someone watching what your endpoints and their AI tools actually do, our managed detection and response service covers Mac fleets alongside the rest of your estate.


← All articles

get in touch

Tell us what you're running

Scoping is free. We reply within one business day, and under 30 minutes for active incidents.