Governing sbx fleets

Two things exist: policies, and the rules inside them. A rule has a decision (allow or deny), an action (connect:tcp/connect:udp for network, read/write for filesystem), and a resource it matches. Policies live at two levels — local (per machine, sbx policy CLI) and organization (Docker Home, or the Governance API). MCP policy is Cedar-based and belongs to wiring-sbx-mcp-servers; this skill covers network, filesystem, audit, and sign-in.

A developer chasing a blocked request should land in diagnosing-sbx-sandboxes. This skill is for the person who writes the policy that blocked them.

The one rule that explains most surprises