Necessary but Unbalanced: A Brief Review of macOS 27.3’s New Permission Controls
macOS 27.3 Beta 2 tightens and refines permission controls for automation tools and AI Agents, adding System & App Protection Override and allowing users to restrict which apps and protected folders they can control. The system also displays permission usage through a blue transparency indicator in the menu bar, but the cumbersome confirmation process, limited prompt information, and beta compatibility issues have sparked controversy. The article argues that the changes better conform to the principle of least privilege, but may also increase the configuration burden and lead to authorization fatigue.
Why read this
AI score 68
Drawing on permission separation, transparency indicators, and community feedback, the article examines the trade-offs macOS makes between the principle of least privilege and the automation experience.
Topics
Body · AI translation
As early as the beginning of October, reports emerged that Apple planned to tighten “Full Disk Access” permissions on macOS because of the privacy risks posed by AI agents. This coincided with tech columnist Jason Aten accusing Meta’s AI agent “Muse” of accessing private information without authorization—although Meta later publicly disputed the claim, insisting that such access would only be possible if Full Disk Access and the information connector had been manually enabled.
However, the change did not actually arrive until macOS 27.3 Beta 2 was released this week, on November 17. Somewhat surprisingly, despite this still being an early beta, Apple simultaneously published a detailed official support document explaining the specific changes.
In short, macOS 27.3 Beta 2 modifies two privacy permissions:
Full Disk Access: A new option allows access to be granted only to specific protected folders, rather than requiring blanket access to the entire disk;
Device Control and Data Access: This has been split into two separate settings: System & App Protection Override and Accessibility.
The most obvious and striking change is the new System & App Protection Override. Whenever software is using this permission to control another application, a blue Live Activity appears in the menu bar—Apple calls it a “Transparency Indicator”—to alert the user that a program is currently exercising the relevant permission.
The most noticeable Live Activity in macOS 27.3 Beta 2
The new “System & App Protection Override” setting
In previous versions of macOS, keyboard remapping, window management, mouse simulation, and various GUI automation tools often had to request the same extremely broad “Accessibility” permission. Although it had already been renamed “Device Control and Data Access” before macOS 27.3 Beta 2, the system still did not distinguish granularly between the operations programs actually needed to perform.
At their foundation, these tools primarily rely on two underlying technologies. One is CoreGraphics-based event injection and keystroke monitoring, such as CGEventTapCreate and CGEventPost; the other is the AXUIElement interface system provided by the accessibility framework, such as AXUIElementPerformAction, AXUIElementCopyAttributeValue, and AXObserver. The accessibility framework was originally designed for assistive tools for people with disabilities, and macOS grants approved programs global permissions by default, allowing them to read the UI elements, control text attributes, and accessibility labels of every running application on the system.
Most automation tools, however, only need to perform operations in specific applications and scenarios. Developers were forced to work through the accessibility framework solely because older versions of macOS lacked a dedicated interface for cross-process UI control. As a result, even a simple click across windows granted far more permission than was actually required—from the user’s perspective, only the program knew what it had accessed, while the user had no way to set limits in advance.
Beginning with macOS 27.3 Beta 2, “Device Control and Data Access” has officially been split into two. The first is “Accessibility,” restored to its original purpose and reserved specifically for accessibility tools such as screen readers, voice control, and assistive controls intended for users with visual or mobility impairments. Apple allows these applications to apply for a dedicated entitlement exemption to retain the simplified authorization process used before the upgrade. The second is System & App Protection Override, intended specifically for automation tools and AI agents that need to control other programs across processes and bypass system protections.
Under the new System & App Protection Override setting, users can further restrict the specific targets a tool is permitted to control. For example, an automation workflow used solely to operate Keynote can be authorized only for Keynote—or, as in 9to5Mac’s example, it can be allowed to access Mail but not Messages. Each target application can also be configured individually as “Ask First” or “At Any Time.”
However, the current interface still has some confusing aspects. Veteran developer Michael Tsai noted that although Apple’s announcement says users can authorize access by “selecting an app from the list to request permission,” there is actually no ready-made app list in Settings, and users must still manually click the “+” button to add a program. Moreover, both this panel and the existing Automation panel use the word “control,” while the separated Accessibility panel still says that apps may be allowed to “control your apps as you do.” The differences among the three are not particularly clear to ordinary users.
For tools that genuinely require broader control, users can also click Bypass System Protections. At present, however, the confirmation process is rather alarmist: macOS displays a huge risk confirmation page requiring users to click red confirmation buttons one by one, acknowledging five categories of potentially high-risk capabilities the program may gain—including reading, modifying, deleting, and exporting all data; viewing hidden and recently deleted photos; browsing the web as you; controlling your Mac, apps, and system settings; and monitoring everything you do, including background windows and every keystroke.
Only after all of these have been clicked does the final approval button become available, after which the user must enter an administrator password or authenticate with Touch ID.
Once access has been granted, you can also revoke a program’s access at any time with a single click. More inconveniently, if you want to reduce an app’s full access to only specific apps or folders, you must first click “-” to remove it and then click “+” to add it again.
Objectively speaking, compared with the previous Device Control and Data Access setting and the still earlier Accessibility setting, the new System & App Protection Override does give users greater flexibility in granting and restricting permissions. But its somewhat overbearing warning interactions, along with certain issues in the beta—such as those noted in Apple’s official macOS 27.3 Beta 2 release notes: interactions with Safari and WebKit apps through this permission may behave unexpectedly, while apps that use CoreGraphics to send input events may also fail to trigger Live Activities properly—still leave considerable room for refinement.
Among the many changes to System & App Protection Override, the blue Live Activity that remains almost permanently in the menu bar while the permission is being used is the most controversial. The rationale behind the design is easy to understand: like the green dot for camera use and the blue location indicator on iOS, it is intended to provide runtime visibility, allowing users to notice immediately when a program performs automated operations in the background through the accessibility interface.
The intention may be good, but in practice it creates a major problem for the already crowded menu bar. As everyone knows, menu-bar space is at a premium on MacBooks with a notch, and macOS’s addition of a conspicuous blue pill icon further reduces the area available to users.
More awkwardly, the Live Activity currently offers very limited functionality: it can only serve as a notification and show which target program is being accessed. It neither reveals exactly what data has been read, modified, or deleted—failing to provide the human-readable audit log that some industry commentators have called for—nor lets users directly undo the automated actions an app has just performed. At most, clicking it takes users to System Settings to readjust permissions. Rather than effectively protecting users, it currently feels more like a persistent visual distraction.
If you rely heavily on trusted automation tools in your daily work and simply cannot stand having this blue pill permanently displayed in the menu bar, 9to5Mac editor Zac Hall has found a temporary Terminal method for hiding it in macOS 27.3 Beta 2. Open Terminal, run the following two commands in order, and enter your administrator password. After restarting your Mac, the internal AX_TRANSPARENCY_INDICATOR feature flag will be disabled without affecting permissions already granted to apps:
sudo mkdir -p /Library/Preferences/FeatureFlags/Domain sudo defaults write /Library/Preferences/FeatureFlags/Domain/TCC AX_TRANSPARENCY_INDICATOR -dict Enabled -bool false
To restore the default display, run the following command and restart again:
Stricter “Full Disk Access” Settings
The old “Full Disk Access” settings in macOS 27.2
As far back as macOS Catalina (10.15) in 2019, a Files & Folders panel was added to System Settings specifically to manage common locations such as Desktop, Documents, Downloads, Pictures, cloud drives, and external volumes. Third-party programs had to request permission from users before accessing these locations. But just as with Accessibility, once a program needed to access a protected path outside the preset directories, users previously often had no choice but to grant it full disk access.
The old “Files & Folders” settings in macOS 27.2
Accordingly, in macOS 27.3 Beta 2, System Settings first explicitly warns: “Full Disk Access is only intended for apps that need to copy or scan all data, such as backup and security software.” When users add an app, the default button no longer grants full disk access directly. Instead, it is now “Choose Folders,” allowing users to manually select specific protected folders outside the preset directories without handing over access to the entire disk.
At the same time, the system has removed two longstanding convenience features:
Previously, when software failed to read a restricted path, it would automatically appear in the Full Disk Access list, waiting for the user to enable it. This mechanism has now been removed;
Many apps also used to place a floating icon on their onboarding screen so users could drag it directly into the settings list. macOS 27.3 has now removed drag-and-drop support as well, meaning users must manually click the “+” button and then locate the program in the file picker.
If users insist on granting a program full disk access, clicking Bypass System Protections still takes them through the same intimidating process of clicking red buttons one by one and authenticating with an administrator password. The only difference is that the risks awaiting confirmation have been reduced to three: reading, writing, deleting, and exporting data; accessing hidden and recently deleted photos; and browsing the web as you. Once approved, the app is also marked with an exclamation point “!” and a red prohibition symbol in the “Files & Folders” list.
It is worth noting that the phrase Bypass System Protections is itself somewhat misleading—the app can still only read files that the current user account already has permission to access; it is not actually bypassing system-level permissions. Apple’s wording seems intended more to scare users away.
Apple has, however, left a path open for essential software such as disk backup tools: developers can apply for a dedicated Entitlement, allowing new users to retain the simple pre-upgrade “Allow / Don’t Allow” experience. Apple says major well-known apps are not currently affected; for example, SuperDuper developer Dave Nanian reports that his app is still working normally for now. But given Apple’s checkered history of taking months—or even more than a year—to review special entitlement requests, developers are broadly skeptical.
Is macOS’s increasingly paternalistic management really a good thing?
Taking a longer view, the changes in macOS 27.3 are really a continuation of the consistent trend over nearly seven years toward an increasingly restrictive macOS permission system that more closely resembles iOS. Consider, for example, the steady tightening of screen recording and screenshot APIs in recent years: macOS Catalina introduced the “Screen Recording” permission in 2019; Apple launched the ScreenCaptureKit framework in 2022 and gradually deprecated the old APIs that allowed silent screen capture; and by macOS Sequoia in 2024, it had even introduced screen-recording authorization prompts for periodic weekly and monthly reviews, thoroughly annoying many users. Only after community protests did Apple relent in macOS 15.1 and stop displaying monthly prompts for authorized screenshot apps used regularly.
Judging by the evolution of screenshot permissions, I expect the blue transparency indicator in the menu bar, which currently feels somewhat performative, to continue evolving over the next few betas and ultimately be reduced to a discreet colored dot, like the indicators for camera and screenshot access.
Another typical example is the successive tightening of local data access permissions. In its early years, macOS was quite permissive about access to local files. That changed with Mojave in 2018, which introduced Full Disk Access for the first time; Catalina in 2019 expanded protection to commonly used directories such as Desktop, Documents, and Downloads, requiring programs to obtain user consent first.
Apple then extended its defenses from user documents to apps’ own data: Sonoma in 2023 began restricting apps from different developers from accessing one another’s data containers; Sequoia in 2024 extended similar protections to shared App Group containers.
By macOS 27, access to app data containers and shared containers across developer teams is denied by default. Even the ~/Library/Application Support directories of some non-sandboxed apps—such as browsers and Discord—have been placed under system-level protection, as detailed in security researcher Wojciech Reguła’s technical analysis.
Yet as permissions become ever more tightly locked down, the usability problems are also becoming increasingly apparent. Many users have independently joked that Apple once ran ads relentlessly mocking Windows Vista’s endless permission prompts, whereas macOS has now become even more troublesome than Vista.
Finally, it is worth looking at the community’s differing views on these changes.
Supporters believe this macOS overhaul does give users more granular control over the data boundaries of various kinds of software and AI Agents, better aligns with the principle of least privilege, and can also pressure developers at the system level to rein in their permission requests.
For example, in a Hacker News discussion, one user took stock and discovered that no fewer than 44 apps on their Mac had requested Full Disk Access—even including the flashcard app Anki and the calculator Soulver—when only eight actually needed it to function properly, showing just how entrenched the abuse of permissions has become. Another commenter noted that, in their race to add features, AI companies bypass standard interfaces for cross-app collaboration and directly scrape underlying files, so it is entirely reasonable for Apple to step in and set rules.
There are already real-world examples of how this can “pressure developers to rein in permissions.” A few days ago, waydabber, the developer of the well-known third-party display control app BetterDisplay, complained on the MacRumors forums that although his app merely wanted to take control of the brightness and volume keys on the keyboard, users had to click through red confirmation buttons one by one on this “scare page” (“FUD page”). It also caused the blue transparency indicator in the menu bar to light up frequently, making it look “like a Christmas tree.”
However, he subsequently updated his response, acknowledging that his initial indignation had been somewhat hasty. The warning had indeed prompted him to reassess BetterDisplay’s permission requirements, and he ultimately found a way to request more narrowly scoped permissions, allowing the app not only to bypass the intimidating confirmation page but also to avoid the blue indicator entirely.
Of course, the opposition has been equally forceful, especially among power users and frontline developers. They argue that the process is not only cumbersome to configure, but also undermines the fast, frictionless automation experience that macOS once offered. Automated tasks that could previously be completed seamlessly by writing a script or using established tools such as Raycast, Keyboard Maestro, Alfred, or BetterTouchTool are now frequently interrupted by permission barriers.
For example, an independent developer on Hacker News complained that because macOS has long lacked sensible, granular APIs, a window-switching utility is forced to request “Screen Recording” permission merely to read a window title, while registering a keyboard shortcut involving fn requires it to masquerade as a keylogger and request “Input Monitoring” permission.
Some users have also questioned the claim that this “puts directory selection in the hands of nontechnical users,” arguing that it is inherently contradictory: ordinary users have no idea which directories an app needs, forcing developers to create dedicated illustrated guides that walk them through the setup step by step. Allowing users to arbitrarily select only certain folders or apps also creates an almost inexhaustible number of permission combinations, turning testing into a nightmare.
In addition, several observers, including Federico Viticci and Michael Tsai, have pointed out a “double standard”: Apple uses layer upon layer of warnings to discourage users from granting third-party AI Agents access, yet its own Siri AI inherently enjoys capabilities equivalent to Full Disk Access. It does not have to go through this cumbersome process and does not even appear in the “Full Disk Access” list.
Ultimately, everyone understands that Apple wants to guard against AI tools that do not play by the rules, but an excessively cumbersome interaction design can easily backfire. Apps have long been accustomed to guiding users step by step through toggling switches in System Settings, and malware can readily follow the same playbook. Just as with the previous barrage of AI access confirmation prompts, once users are worn down by an endless stream of red buttons and secondary confirmations and succumb to “consent fatigue,” they will most likely choose the path of least resistance in the future: clicking through everything with their eyes closed, just as they did before, and handing over all permissions outright.
AI Trends