Apple tightens Mac permissions as agents ask for the whole disk

Apple has redesigned the two macOS settings that decide whether an app can reach everything on a Mac. In macOS 27.3 beta 2, Device Control and Data Access splits in two, users can require an app to ask every time it needs access, and a new indicator appears when one app controls another. The change constrains what a local agent can touch. It does not tell a service who that agent is.

What happened

On 16 November 2026 Apple published a developer notice, “Updates to Device Control and Data Access, and Full Disk Access in macOS”, describing changes shipping in macOS 27.3 beta 2. The notice lists six:

  • Device Control and Data Access splits into two settings: System & App Protection Override, and Accessibility.
  • A single method for granting permissions, by selecting the requesting app from a list.
  • Guidance encouraging users to grant access only to the specific apps or folders a workflow needs.
  • More visibility into the range of data an app will be able to read or control if full permissions are granted.
  • An option to configure apps to ask every time they require access.
  • A transparency indicator when a requesting app is controlling another app through System & App Protection Override.

Apple also told developers to adjust onboarding so apps “gracefully handle having access to only a limited set of folders or apps”, and said developers who need Full Disk Access for disk backup, or the Accessibility settings for assistive technology, can request entitlements to preserve their previous behaviour on new installs. Permissions already granted by users remain in effect. Apple’s notice frames the work as data protection and privacy; it does not use the word agent.

The agent framing comes from Apple’s earlier announcement and from the coverage around it. TechCrunch reported on 2 October that Apple would tighten macOS Full Disk Access controls “due to new risks from AI agents”, and on 16 November connected the shipped changes to that promise. The same reporting cites two incidents behind the concern: a journalist’s claim that Meta’s Muse app read private messages without consent, which Meta disputed, and a Wired report of a flaw in ChatGPT’s Mac app that could have exposed sensitive data.

Why it matters for KYA

Agents that run on a person’s machine do not arrive with a credential a website can check. They arrive as processes inside an app, and they inherit whatever that app has been granted. That is the structural point behind Apple’s change: the operating system can decide which folders and which other apps a program may touch, but the unit it identifies is the app, not the agent, the task, or the person on whose behalf the task is running.

The every-time prompt is the closest thing here to per-action authorisation, and it is worth being precise about what it is. It is consent, collected at the moment of access, by a human looking at a dialog. It is not evidence. It does not bind the approval to a task, an amount, a counterparty or an expiry, and it does not produce a record that a third party can verify after the fact. A prompt that a user clicks through forty times a day is a prompt that stops being read — the consent-fatigue problem regulators now name explicitly.

The transparency indicator is useful and limited in the same way. It shows a user, in the interface, that one app is driving another. That is a real improvement over silent control. But a UI indicator is not an audit trail: it is not signed, not retained, and not available to the service on the other end of the connection. For KYA, the interesting question is whether an OS-level grant ever becomes a machine-readable statement — this app, this agent, this scope, this expiry — that can be presented and checked elsewhere. Nothing in this release does that.

What the release does do is sharpen the blast-radius calculation. If an agent runs inside an app holding Full Disk Access, the agent’s effective authority over local data is the app’s authority, not the task’s. Separating agent workloads into their own app identity, granting the narrowest folder set that works, and keeping a record of which app held which grant at what time are the practical controls available today — and they are the same controls an auditor will ask about after an incident.

What to watch

  • Whether macOS exposes grants and overrides in a machine-readable form — a log, a profile, an MDM-visible inventory — rather than only in System Settings. Without that, enterprise review stays manual.
  • Whether agent frameworks document the entitlements they need, instead of asking users to grant Full Disk Access and hoping. The onboarding guidance Apple published puts the burden on developers.
  • Whether the ask-every-time option survives contact with real workflows. If vendors instruct users to turn it off to make their agent usable, the control exists on paper only.
  • Whether any of this connects to the identity layer — an agent identifier that a website or API can verify — or remains a local permission model. The two are complementary, and only one of them is being built here.

Sources

  • Apple Developer, “Updates to Device Control and Data Access, and Full Disk Access in macOS”, 16 November 2026 — developer.apple.com
  • TechCrunch, “Apple reveals new Mac security controls as AI agents raise privacy risks”, 16 November 2026 — techcrunch.com
  • TechCrunch, “Apple says it’s tightening macOS Full Disk Access controls due to new risks from AI agents”, 2 October 2026 — techcrunch.com

Know Your Agent (KYA) explains agent identity, verification and accountability. This is an explainer, not legal or compliance advice — see our Sources & methodology. New to KYA? Start with What is Know Your Agent? and the glossary.