Docs.

Install it, run your first sandboxed server, then go deep on the policy schema. Start with Install and Quickstart — in that order.

Install→

Linux, macOS, Windows, Docker fallback — or build from source with Go 1.22+. What each platform needs before warden will run.

Sandbox your first MCP server in five minutes: copy a fixture policy, run it, then trace-and-generate for your own servers.

Every policy.yaml field, validation rule, and enforcement note — the one reference to keep open while writing policies.

run, trace, init, logs, gateway, --approve — every subcommand and flag, verified against the source.

18 tested servers with exact policies: 14 pass, 2 conditional, 2 fail with classified reasons.

Missing backends, bare npx commands, blocked access, the HOME footgun, and what Warden can't do.

How the CLI, policy engine, sandbox backends, egress proxy, and audit logger fit together — with component diagrams.

Copy-paste policies for filesystem, GitHub, Slack, PostgreSQL, Brave Search, and a comprehensive reference template.

Threat model, known limitations, credential exposure risks, and best practices before relying on any policy in production.

M0 through M8 milestones — what's built, what's shipped, and what's next for Warden.

Development setup, pull request guidance, and the three highest-impact contribution areas right now.

Unit tests, integration tests, escape tests, fixtures, and CI expectations for the project.

Test Warden on Linux, macOS, and Windows — build binaries, run MCP servers, verify security boundaries.