The first time an app asks to use the camera or the microphone, macOS shows a single prompt: allow it, or don’t. Tap Allow, and unlike a cookie banner, that answer sticks — the app won’t ask again. Here is what that click actually decides, where to go back and change it, and the one thing changing it does not do.
What the one-time prompt actually decides
Apple describes the control point this decision feeds: in Settings on macOS, users can see which apps they’ve permitted to access certain information as well as grant or revoke any future access. In practice, that means the prompt you answer once is recorded, and macOS uses that record every time the app tries again — it won’t ask twice unless you, or the app’s reinstallation, or a reset changes the record.
Where to review it, and switch it off
Go to Apple menu › System Settings › Privacy & Security › Camera, and the same page for Microphone. Apple’s own instructions: “Turn access to the camera on or off for each app in the list” — and the equivalent for the microphone. Every app that has ever asked is listed, with its own switch, so you can turn access off for one app without touching the rest.
Resetting it from the terminal
macOS also ships a command-line way to reset that record: tccutil. Its own manual page describes what it does plainly: it “manages the privacy database, which stores decisions the user has made about whether apps may access personal data,” and its reset command resets those decisions so the app is asked again.
tccutil reset Camera com.example.appWhat revoking access does not do: stop a call already in progress
Turning access off, or resetting it with tccutil, decides what happens the next time that app tries to use the camera or microphone. It does not reach into a session that is already running: if an app currently has the camera or microphone open, changing the permission is not a reliable way to end that session immediately. Quitting the app is the direct way to stop a live capture right now.
FireAI’s “Stop it” menu
FireAI 0.1.2 shows the moment an app turns the camera or microphone on, and puts the same three responses in one place, next to that session:
- Remove that app’s camera or microphone access on the spot, the same way
tccutildoes it — macOS will ask again the next time the app wants it. - Quit the app outright, which is what actually ends a capture that is already running.
- Block the app’s internet access with a FireAI rule, reversible at any time, so nothing it records can leave the Mac even while the camera or microphone stays open.
The short version
Allow is not forever, and it is not instant either. System Settings and tccutil change what happens next time; only quitting the app reliably ends what is happening right now. FireAI’s “Stop it” menu keeps all three actions, plus the network one, in the same place.
How FireAI and HisnLabs fit in
Turning access off or resetting it with tccutil decides what happens next time; it does not reach into a session already running. FireAI 0.1.2 adds that last step: a “Stop it” menu that removes an app’s camera or microphone access, quits the app, or blocks its internet outright.
FireAI is HisnLabs’ own product: an on-device AI firewall for Mac. It shows every connection your apps make, in plain language, and lets you decide what leaves your Mac — its AI runs locally, so your traffic is never sent to us or anyone else. HisnLabs’ security research team is the group that keeps that decision-making accurate: cataloguing which domains are ordinary telemetry versus a real product, tracking the country and network behind a connection, and training the on-device model (its Autopilot feature) on real traffic patterns, all without any of it leaving your Mac.
You can read the technical decisions behind it, or try FireAI for 17 days, at FireAI, by HisnLabs.