MCP on macOS · Roadmap
Desktop AI tools with real boundaries.
macOS-native sandboxes for MCP servers. File, process, and network limits enforced by the OS. No Docker.
DORA.TPRM-02Roadmap: not part of this control’s evidence today. See what ships now.
Sandbox launch config
json
{
"mcpServers": {
"native-container": {
"command": "/usr/bin/sandbox-exec",
"args": [
"-f", "~/.mcp/config/mcp.sb",
"node", "~/.mcp/server/server.js"
]
}
}
}01Operating model
Local agents need boundaries too.
- Real sandbox, no Docker
- macOS sandbox-exec constrains file, network, and process access.
- Explicit permissions
- Declare paths and endpoints the MCP server can reach. Everything else is denied.
- No parallel governance path
- Local isolation. Same governance contract as the CLI and cloud workers.
02Architecture
How the sandbox wraps MCP execution
Execution flow
03Security posture
Deny by default
Deny everything, then grant explicitly, as IAM and VPC do in the cloud.
Filesystem
Scoped to declared project paths.
Network
Outbound blocked by default; only declared endpoints open.
Lifecycle
Supervisor-managed launch and logging.
scheme
(version 1)
(deny default)
(allow file-read* (subpath "/Users/yourname/projects"))
(allow process-exec (literal "/usr/local/bin/node"))Need something you can run today?
The validated AWS path covers capture, approvals, and audit today.