macOS 27.3 beta 2 introduces more detailed warnings when an app requests Full Disk Access. The updated explanation helps users understand that an authorized app may read, modify, delete, or export files, and may access sensitive items such as browser history and hidden or recently deleted photos. The change is especially relevant to AI agents, which can take actions across files and apps rather than simply answer questions.
What does Full Disk Access allow an app to do?
Full Disk Access gives an app broad access to protected data on a Mac. Depending on the app and the files involved, it may be able to read, change, delete, or export information. The revised beta warning describes the scope in more concrete terms so users can assess what granting permission may mean.
- Read files: An app may inspect documents and other protected data.
- Modify or delete files: An app may alter or remove information, not just view it.
- Export data: An app may copy information to another location or service.
- Access sensitive content: The warning calls attention to items such as browser history, hidden photos, and recently deleted photos.
- Perform actions through an account: Some apps may interact with browser activity or carry out online tasks on a user’s behalf.
Why are AI agents a particular concern?
An AI agent can do more than generate text. When a user authorizes it, the agent may search files, edit documents, move information between applications, or initiate online actions. Those capabilities can save time, but broad access also increases the consequences of a mistaken instruction, flawed automation, compromised update, or software bug.
For example, an agent asked to organize a project folder might read several documents and produce summaries. If it also has permission to export files, sensitive content could be copied to an unintended destination. A personal assistant that searches email may be useful for drafting replies, but its access should be limited to what the task actually requires.
Does running an AI model locally eliminate privacy risks?
No. A local model can process information on the Mac instead of sending it to a cloud service, which may reduce exposure during processing. However, local processing does not automatically restrict the permissions of the app that runs the model. If that app has Full Disk Access, it may still be able to reach and export a wide range of local data.
For instance, a local model might summarize email without uploading messages to a provider. If its host app has broad system permissions, the app’s access still warrants scrutiny. Local execution and least-privilege permissions address different parts of the privacy picture.
How to review Full Disk Access on a Mac
- Open System Settings and go to Privacy & Security.
- Open Full Disk Access and review the apps listed there.
- For each app, consider whether its stated purpose requires access to protected files.
- Read the permission warning carefully and check which types of information the app may reach.
- Turn off access for apps that do not need it, and revisit permissions after installing or updating software.
Menu names and layouts can change between macOS versions. If a setting appears in a different location on your Mac, use System Settings search to find “Full Disk Access.”
Which apps should users examine most carefully?
AI assistants and agent-based tools deserve particular attention because they can combine file access with automated actions. File tools organizers, backup utilities, data-analysis, and photo apps may also have legitimate reasons to scan large collections, but users should check whether the requested access matches the app’s function.
A useful test is to ask what the app cannot do without this permission. If a narrow feature requires access only to selected files, look for a file picker or another limited-access option rather than granting system-wide permission. Reassess the choice if an app requests broader access after an update or changes its behavior.
How can users reduce the risks of broad app permissions?
- Grant access only when necessary: Decline requests that do not support a feature you intend to use.
- Prefer limited access: Use a file-selection workflow when it meets the need instead of authorizing access to the whole disk.
- Review permissions periodically: Remove access from apps you no longer use.
- Keep backups: Maintain a separate, recoverable copy of important files in case an app alters or deletes data unexpectedly.
- Check app behavior: Pay attention to unexpected file changes, exports, or network activity.
What does the macOS 27.3 beta change mean?
The beta makes the consequences of Full Disk Access easier to understand by spelling out the kinds of data and actions involved. It does not remove the permission or guarantee that every app will use access responsibly. Instead, it gives users more context when deciding whether to approve a request.
Because macOS 27.3 beta 2 is prerelease software, its interface and wording may change before a final release. Users should treat the new warning as a clearer explanation of a powerful permission, not as a substitute for reviewing which apps have access.
Frequently asked questions
Is Full Disk Access always required? No. An app needs it only when its functions require access to protected data beyond narrower permissions. Many apps can work with access to selected files instead.
Can an app with Full Disk Access delete or export files? The beta warning explains that access can include modifying, deleting, and exporting data. The exact actions depend on the app and how it is designed.
Is a local AI app automatically private? No. Processing data on the Mac can avoid sending it to a cloud service, but the app may still have broad access to local files if the user grants Full Disk Access.
How do I revoke Full Disk Access? Open System Settings, select Privacy & Security, choose Full Disk Access, and switch off access for the app. Labels and navigation may differ across macOS versions.

Be the first to comment