Developer Tools (Developer Tools) is a macOS privacy permission. Developer Tools permission allows an app to run software that doesn't meet the system's normal security policies — such as unsigned code, code without hardened runtime, and debugging tools. This is primarily needed by developers using Xcode, Terminal, or other development environments. Common apps that request this permission include Xcode, Terminal, iTerm2, Visual Studio Code, Android Studio. Risk level: safe. To check which apps have this permission, open System Settings, go to Privacy & Security, and select Developer Tools. CoreLock identifies apps with Developer Tools access and flags any non-development apps that have been granted this permission. Since this permission lowers macOS security guardrails, CoreLock ensures only legitimate development tools have it.
Developer Tools permission allows an app to run software that doesn't meet the system's normal security policies — such as unsigned code, code without hardened runtime, and debugging tools. This is primarily needed by developers using Xcode, Terminal, or other development environments.
Click the Apple menu and select System Settings.
Click Privacy & Security in the sidebar.
Click Developer Tools. This shows apps that are allowed to run code that doesn't meet normal security policies.
Only actual development environments and terminal emulators should be here. If you're not a developer, this list should be empty.
Go to System Settings > Privacy & Security > Developer Tools.
Disable the toggle for any app you want to restrict. The app will no longer be able to run unsigned or unnotarized code.
If you're doing development work, you can re-enable it. Consider toggling it off when you're not actively coding to reduce your attack surface.
CoreLock identifies apps with Developer Tools access and flags any non-development apps that have been granted this permission. Since this permission lowers macOS security guardrails, CoreLock ensures only legitimate development tools have it.
Almost certainly not. If you don't write code or use development tools, this list should be empty. If you see apps here that you don't recognize, remove them. This permission lowers macOS security protections for those apps.
It lets approved apps run code that hasn't been signed or notarized by Apple, attach debuggers to running processes, and bypass certain hardened runtime restrictions. This is necessary for software development but reduces security protections for those apps.
Yes, if you're using it for development. VS Code needs this permission to run and debug code, use integrated terminals, and work with extensions that execute code. It's a legitimate use case from a trusted developer (Microsoft). Just be cautious about which VS Code extensions you install.
CoreLock scans every app on your Mac and shows you exactly which permissions each one has. Find hidden access in under 60 seconds.
Download CoreLock FreeAvailable for macOS and Windows