sandbox-configurator

Sandbox configuration enforces file system and network isolation boundaries through JSON templates. Define security levels (maximum, balanced, or development), specify trusted domains, control command restrictions, and apply Docker and Unix socket rules to protect against malicious code execution.

Three granular security modes are available: maximum isolation for strict restrictions, balanced mode for full-stack development with Docker and local servers, and development mode for relaxed policies. Each level controls file access, network binding, and excluded command lists.

Yes. Balanced security mode lets you configure trusted domains, enable local binding for dev servers, and integrate Docker while blocking unauthorized network interactions. Excluded commands bypass sandbox restrictions for necessary integrations.

The Skill provides audit-ready documentation, environment variable handling, and validation steps. Configurable isolation levels and command restrictions satisfy security policy engine requirements for controlled file system and network access in regulated environments.

Define specific commands in the excluded list—such as git or docker—to operate outside sandbox boundaries. This enables necessary integrations while maintaining isolation for all other operations.

Docker is optional and controlled via configuration. The Skill supports Docker integration through excluded commands and socket controls, but sandbox isolation works with Unix socket configurations and file system rules independent of Docker.