# A Wolf at the Door: Apple Is Rethinking Mac Permissions for the Age of AI Agents

> Source: <https://macanorak.com/a-wolf-at-the-door-apple-is-rethinking-mac-permissions-for-the-age-of-ai-agents/>
> Published: 2026-11-18 10:00:05+00:00

[Field Notes](https://macanorak.com/tag/field-notes/)

# A Wolf at the Door: Apple Is Rethinking Mac Permissions for the Age of AI Agents

Following the furore surrounding Meta’s Muse and the appetite of AI agents for access to our personal data, Apple promised to tighten macOS privacy controls. Now we know what it’s planning.

Back in October, I wrote about Meta's new AI agent Muse under the rather unflattering title [A Wolf in Terrycloth Clothing](https://macanorak.com/a-wolf-in-terrycloth-clothing/), which was a reference to its (no doubt deliberately) disarming mascot.

I wasn't impressed with Meta's approach to privacy, to say the least. I was actually pretty angry. I was especially exercised about the extraordinary permissions these new AI agents were requesting. The ability to access your messages, your email correspondence, photos, browsing history and other personal information is one thing. But letting an increasingly autonomous piece of software interpret that information and act on your behalf is quite another thing.

There were some rather alarming examples of what could go wrong. [One user](https://x.com/MattRobbt/status/2104798102037074212?ref=macanorak.com), Matt Robb, discovered that Muse had been given permission to send messages containing his home address to strangers. He subsequently explained that he had selected an *Allow Always* option, believing that he would still have the opportunity to approve certain actions. That permission allowed Muse to send messages containing his address. Another user, journalist [Jason Aten](https://www.inc.com/jason-aten/metas-new-muse-ai-agent-read-my-private-messages-i-never-asked-it-to/91408202?ref=macanorak.com), reported that Muse had synchronised a substantial portion of his Apple Messages database, despite his understanding that Full Disk Access was switched off. (Meta disputes this account, by the way).

The whole sorry business prompted considerable discussion online, especially after Apple announced it intended to introduce additional controls around Full Disk Access in macOS. Disquiet and gnashing-of-teeth followed. Would Apple make life difficult for developers?! Would perfectly legitimate applications such as Alfred or Hazel be caught in the crossfire?! Was this going to be another example of Apple deciding that it knew better than its users?!

Well, we now have a clearer picture. On 16 November, Apple announced the changes in macOS 27.3 beta 2. They're much more nuanced than just adding another warning dialogue to System Settings, and much less scary than the doomsayers were prophesying.

**Full Disk Access**

Full Disk Access has been part of macOS for some time now.<sup>[\[1\]](#fn1)</sup> It's a permission that allows applications to access files and information that would otherwise be protected by the OS. There are, of course, perfectly legitimate reasons for this: backup utilities need to access files throughout your Mac; security applications need to inspect areas of the file system that ordinary apps can't reach; disk utilities, file indexers, and automation tools may also require access to information beyond the usual application sandbox. It's a part of what makes the Mac a flexible platform.

Full Disk Access has historically been one hell of a powerful permission. Grant it to an application and you're potentially giving it access to your messages, emails, photos, browsing information and any data belonging to other user accounts. It can read, change, delete and export that information. That's an awful lot of trust to place in a single piece of software, especially when you consider how much personal information most of us keep on our Macs. (They're called *personal computers* for a reason).

But — and this is a pretty important ‘but’ — granting an application Full Disk Access doesn't mean it will necessarily do all those things, it means macOS has given it the *ability* to do them. What happens next greatly depends on the application itself, how it's been designed, and what the company operating it intends to do with the information it obtains.

This wasn't so much of a problem when the application requesting access was a conventional backup utility — we understood broadly what it was doing and why it needed the permission. But AI agents have changed the equation.

**Giving an agent the keys.**

An AI agent doesn't simply wait for you to ask a question and return an answer — it can proactively undertake tasks, interact with applications, interpret information, make decisions, and take actions on your behalf. It's like a butler that you leave to take care of certain tasks while you're out of the house.

An AI agent might need to inspect your email correspondence to identify an outstanding task, look through your calendar to find a suitable appointment, or examine documents to prepare a report. The more useful we want AI agents to become, the more information and control they're likely to need. But should an agent that needs to organise your emails also be able to inspect your private text messages? Should an application that helps you manage your files have access to your financial records? And should it retain all those permissions indefinitely, even when it only needs them occasionally?

Returning to my hypothetical butler: if I were to ask him to tidy up my bedroom, is that the same thing as giving him permission to rifle through my bedside drawer? And what if the butler is secretly a wolf in butler attire, harbouring malign intent?

An application doesn’t have to be malicious for this to become a problem. We’re giving increasingly sophisticated software permissions that were designed for a rather different kind of application. There's also the question of whether users *genuinely understand* what they're agreeing to. Consent isn't meaningful if the person giving it doesn't understand its consequences. Apple appears to have reached much the same conclusion.

**What exactly is Apple changing?**

There are [two related areas of macOS permissions being updated in 27.3](https://support.apple.com/en-us/149699?ref=macanorak.com). The first is Full Disk Access itself. The second is a separate permission previously called Device Control and Data Access. Apple is also introducing a single, consistent method for granting permissions, allowing users to select the application requesting access from a list.

1. ***Full Disk Access becomes more granular.***

Previously, if an application required Full Disk Access, you essentially had to decide whether it could access everything, or not. It was a rather all-or-nothing, take-it-or-leave-it type of arrangement, akin to giving a butler the key to your entire house, or no key at all. Under the new system, Apple is introducing the option of granting access to specific protected folders instead.

Imagine an application that needs to work with documents in your Documents folder. Why should it need access to Photos, Messages and everything else on your Mac? With macOS 27.3 beta 2, where supported, users will be able to *pick and choose* the particular protected folders an application is allowed to access.

This is the application of something known in security circles as the ‘[principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege?ref=macanorak.com)’. The idea is straightforward: an application should receive only the permissions it needs to perform its intended function, rather than being given unrestricted access simply because that's the easiest way to make it work.

This is hardly a revolutionary concept, but I personally like the fact that Apple is making it easier for ordinary users to implement it, without needing to understand all the intricacies of macOS security.

The option of granting broader access remains available. Apple’s support documentation makes the implications rather clearer than before — it explains that an application with this level of access can read, change, delete and export all your data, including information you might not ordinarily think of as files on your Mac. That includes hidden and recently deleted photos, for example, and information about your browsing activity. Apple is now encouraging users to *carefully consider* whether an application actually needs that much access.

Apple’s documentation says that the ability to select specific folders or applications only appears for certain applications. Other applications, including some backup utilities and assistive technologies, can still require broader permissions.

1. ***Device Control and Data Access gets split in two.***

This is perhaps the most significant change. Apple previously had a unified permission called Device Control and Data Access. This covered capabilities that could allow applications to interact with other applications and exercise considerable control over the Mac. We're talking about things such as controlling applications, monitoring keyboard input, accessing information displayed on screen and interacting with other parts of the operating system. Big stuff.

In macOS 27.3 beta 2, Apple is splitting this into two very separate things.

- 
**Accessibility:** This is intended for assistive technologies such as screen readers and voice control applications, that sort of thing. These applications have legitimate reasons to interact with the operating system in ways that ordinary applications can't. Apple (rightly) wants to preserve that functionality while separating it from the much broader capabilities associated with application automation.
- 
**System & App Protection Override:** This is the one that's more germane in the context of AI agents. It allows applications to bypass certain macOS protections so that they can control other applications and perform automated tasks. Users can now*choose* which applications an automation tool is permitted to control. For example, you might want an AI agent to interact with Mail, but have absolutely no good reason to allow it to control Messages, Photos or Safari. You can now grant access to the applications that are actually required for the task.

Apple’s support documentation says:

When you give an app System & App Protection Override, you can choose specific apps for it to control. If you allow it to bypass system protections instead, it can fully control your Mac and apps, which allows it to access all of your data. It can also see every window and app, including ones in the background, and capture every keystroke.

1. ***You can make an agent ask before controlling an application.***

When granting System & App Protection Override, users will be able to configure access to individual applications in one of two ways.

- **Ask First:** the application must request your permission before controlling the selected application.
- **At Any Time:** the application can control it without asking for further permission again.

Of course, there is a trade-off. An agent that has to stop and ask permission is a rather less autonomous agent. If you're trying to automate a complicated workflow, repeated permission requests could become onerous. But to be honest, there are certain things we shouldn't want our computers doing entirely unsupervised.

1. ***A visible indicator when applications are being controlled.***

Apple is also introducing a privacy indicator in the menu bar when an application is controlling another application using System & App Protection Override. Think of it like the orange dot that appears when an application is using the mic, or the green dot that appears when it’s accessing the camera.

This is a small but welcome change. One of the difficulties with autonomous software is it can do things in the background, outside our immediate field of attention. A visible indicator doesn't tell you everything the agent is doing, but it does provide a useful indication that another application is exercising control over your Mac. I'd rather have that than find out later that something has been happening without my knowledge.

**Permission is not consent.**

In my October Field Note, ["Allow Always" —AI Agents Have a Consent Problem](https://macanorak.com/allow-always-ai-agents-have-a-consent-problem/), I explored the uncomfortable gap between what users *believe* they've authorised an AI agent to do and what the agent *actually does in practice*.

At the heart of that argument was a straightforward question: is the permission we’re giving an AI agent actually understood, specific and meaningful? I borrowed from the FRIES framework for consent (Freely given, Reversible, Informed, Enthusiastic and Specific) and applied it to a series of incidents involving Meta's Muse, banking apps and Dots — OpenAI's own coding agents. They didn't fare particularly well.

Apple's new controls address some of these concerns, especially the need for permission to be specific and, to a degree, reversible. Being able to grant an agent access to Mail without automatically giving access to Messages is an improvement, but giving an agent permission to control an application is not the same as giving permission for the agent to do anything it likes within it.

An agent might legitimately have access to Mail, for example, but that doesn't mean it should be able to send an email disclosing your home address, or forward confidential correspondence, or delete important messages without further approval.

In my Allow Always piece, I suggested that agents should be allowed to “*look but not touch*”, with explicit approval required before consequential actions took place. I still think that's a good starting point. Apple's changes help to establish *boundaries* about what an agent can access and control. They don't by themselves establish what it should be allowed to do with that access.

**What about Alfred, Hazel and all those other Mac utilities?**

When Apple first announced its intention to tighten controls for this access there was concern that legitimate applications could be affected. [John Voorhees at MacStories](https://www.macstories.net/linked/apple-announces-plan-to-impose-new-full-disk-access-controls-on-mac-developers/?ref=macanorak.com) raised the possibility that established utilities such as Alfred<sup>[\[2\]](#fn2)</sup> and Hazel might find themselves swept up in the changes.

The Mac has always had a relatively open and flexible application ecosystem. Developers have been able to create powerful utilities that interact with files, applications and system services in ways that simply aren't possible on an iPhone or iPad. We absolutely shouldn't lose that flexibility in the name of security.

Apple has addressed some of these concerns in its announcement.

First, permissions that users have already granted will remain in effect. Applications aren't suddenly going to lose access simply because you've installed macOS 27.3 beta 2. Second, Apple says that currently known applications won't be affected and will retain their existing experience without needing an entitlement. Third, developers of backup applications that use Full Disk Access and assistive applications using the new Accessibility settings can request entitlements to provide the same experience for new installations.

Apple says further details about these entitlements will follow. At this stage there's no reason to assume that Alfred, Hazel or your other favourite established Mac utility is about to stop working. But developers will need to ensure their applications can cope with more restricted permissions. Apple explicitly says they should be prepared to adjust their onboarding processes, and handle situations where users grant access to only selected folders or applications.

Apple appears to be drawing a distinction between applications that genuinely need extensive access and those that simply request it because it’s convenient.

There’s one other caveat worth mentioning: these changes don’t automatically revoke permissions you’ve *already granted*. Apple says existing permissions remain in effect. So if you’ve previously given an application unrestricted Full Disk Access, installing macOS 27.3 beta 2 won’t suddenly restrict it to particular folders. You’ll need to review those permissions yourself. It’s probably a good opportunity to have a look through your Privacy & Security settings and think carefully about which applications really need the access you’ve given them.

**Has Apple actually solved the problem?**

In all honesty, not entirely. And this is where I can't allow myself to get completely carried away with enthusiasm for Apple's changes.

Permissions are only one part of the privacy equation. Consider what happens when an AI agent is given access to your email. Even if you restrict it to Mail and prevent it from accessing Messages, it could still encounter extraordinarily sensitive information: financial details, medical correspondence, personal conversations, confidential business information, etc. Your email account is probably one of the richest sources of personal information on your Mac. Once an agent has accessed that information, revoking its permission doesn't undo what's already happened.

If I allow my hypothetical butler to look through the mail in my physical mailbox, I can't suddenly have the butler ‘forget’, or un-see what he’s read and seen. Similarly, the AI agent might have processed the information from Mail, generated summaries, transmitted data to a remote service or incorporated it into an ongoing task. So whilst macOS can control what an application is about to access, it can't by itself guarantee what happens to information after an application has legitimately obtained it.

There's also the question of where the AI processing takes place. Some agents operate primarily using cloud-based models; others offer local processing, or a combination of the two. Again, there's a difference between my hypothetical butler reading my mail and keeping that information to himself, and sharing it around with all his other butler friends.[\[3\]](#fn3)

These are questions that developers need to answer clearly, and users need to start asking them. We need to understand what an application wants access to, why it wants it and, perhaps more importantly, what it’s going to do with the information once it has it.

**The Mac is changing, and so is the meaning of trust.**

For decades, one of the Mac's great strengths has been its flexibility. It allows users to install powerful utilities, automate complicated workflows, and make it behave in ways that Apple might never have anticipated.

But AI agents are fundamentally changing the relationship between users and their software. Applications are no longer simply waiting for us to tell them what to do — they’re beginning to interpret what we want, find the information they need, proactively make decisions and act on our behalf. And the more we expect these agents to do, the more access they're very likely to require.

Giving an AI agent access to your emails, photos, files and browsing history means giving it access to an extraordinary amount of your personal life. We should be asking whether an application genuinely needs access, whether it needs all of it, and whether we're comfortable with what it might do once it has it.

Apple clearly recognises that its existing permissions model wasn’t designed with this new generation of software in mind. Of course, we don’t want a Mac that’s so restricted that developers can’t build genuinely useful applications. But neither should enjoying the benefits of AI mean handing over access to virtually everything we do.

Apple, as it often does, appears to be trying to find a moderate, middle ground. It isn't taking Full Disk Access away — it's making the decision to grant it more informed, more deliberate and where possible, more specific,

If we're going to invite autonomous software into our personal lives, we need to be rather more thoughtful about what we're allowing it to see and do.

Personally, I rather like having a door to my home that locks. It keeps the wolf from getting in.

1. Full Disk Access was introduced on the Mac with macOS 10.14 Mojave in 2018. [↩︎](#fnref1)
2. On the subject of butlers, I'd always imagined that the Alfred app was so named as an allusion to Batman's butler, Alfred. Sadly, according to the developers, [there is no such connection](https://www.alfredforum.com/topic/21979-why-the-name-alfred-for-this-app/?ref=macanorak.com) .[↩︎](#fnref2)
3. Do butlers have a network? A Union? I like to think so. There is this: [The International Guild of Professional Butlers](https://butlersguild.com/?ref=macanorak.com) . Be warned — treat your butlers with care.[↩︎](#fnref3)
