AuraOne / Docs / Agent Studio Open / Security
Sandbox guide
Run untrusted stdio MCP servers with declared paths and limited network/file access.
At a glance
Agent Studio Open guide
- Entry
- Sandbox guide
- Reading
- 8 min
- Sections
- 1
- Applies to
- Applies to the current Agent Studio Open source release. Check the product page and repository for the latest version, supported platforms, and installation details.
01
When to enable sandbox mode
Enable sandbox mode when testing a server from an unknown repository, a server with destructive tools, or a server that requests broad filesystem access.
Sandbox mode is a guardrail, not a proof of safety. Review linter findings, inspect the manifest, and run sample calls against disposable data first.
- macOS uses sandbox-exec profiles for declared paths.
- Linux uses bubblewrap when available.
- Remote SSE/HTTP servers cannot be sandboxed locally; restrict headers and use disposable keys.
- Sandbox rejection errors include the denied path or capability when the platform exposes it.
# Sandbox controls are a desktop feature, not CLI flags.
# The published CLI can still scan source before execution:
agentstudio risk-scan ./server --format json --fail-on high