seatbelt-sandboxer

Generate and iteratively test Seatbelt sandbox profiles for macOS applications.

6.5k|561|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/trailofbits/skills --skill seatbelt-sandboxer-trailofbits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: seatbelt-sandboxer
Source: https://github.com/trailofbits/skills/tree/main/plugins/seatbelt-sandboxer/skills/seatbelt-sandboxer
Command: npx skills add https://github.com/trailofbits/skills --skill seatbelt-sandboxer-trailofbits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of manually creating macOS Seatbelt sandbox configurations for applications, reducing the time and effort needed for sandboxing.

Core Features & Use Cases

  • Application Isolation: Automatically generate configurations for macOS applications that need to be sandboxed for security purposes.
  • Customizable Profiles: Users can customize profiles to specify required resource access like file, network, and process permissions.
  • Quick Start: With a simple instruction, the Skill generates a profile for any macOS application.

Quick Start

Use the 'seatbelt-sandboxer skill with a description of your app, like "Create profile for Finder". Provide additional requirements like 'need_network' and 'can_access_network' to adjust permissions.

Frequently Asked Questions about seatbelt-sandboxer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a macOS Seatbelt sandbox profile for an application?

To generate a macOS Seatbelt sandbox profile, provide the application name and its required permissions. The tool identifies resource requirements like file I/O and network access, then iteratively creates and tests the profile.

What is the best way to isolate a macOS application using a Seatbelt sandbox?

The best way to isolate a macOS application is by generating a minimal Seatbelt profile. This automatically restricts resource access across categories like process execution and Mach/POSIX IPC based on application requirements.

Can I customize Seatbelt profiles to allow network access and file I/O for specific macOS apps?

Yes, you can customize Seatbelt profiles by specifying requirements like 'need_network' or 'can_access_network'. This adjusts permissions for file I/O, network access, and process execution within the macOS application sandbox.

How does the iterative testing process work when creating macOS sandbox configurations?

The iterative testing process works by generating a preliminary Seatbelt profile, testing it against the application's operations, and refining the resource permissions until the macOS sandbox configuration functions correctly without breaches.

Do I need to manually define Mach/POSIX IPC permissions for macOS application sandboxing?

No, you do not need to manually define Mach/POSIX IPC permissions. The profile generation automatically identifies and handles these inter-process communication requirements during the macOS sandbox creation process.

What are the limitations of automatically generating minimal macOS Seatbelt profiles?

Limitations of automatically generating minimal Seatbelt profiles include potential inaccuracies if application requirements are not thoroughly specified. Complex IPC or dynamic file access patterns may require manual profile adjustments after generation.