Warden documentation
Run local tools with only the files, network destinations, environment variables, and resources they need. Start with the quickstart or protect an AI coding agent with a sanitized workspace.
Start here
Install Warden, write a small policy, and run your first protected local command.
Protect an AI agent
Let a coding agent work on a sanitized project copy while protected values stay hidden and host changes require review.
Write a policy
Choose the files, hosts, environment names, and runtime limits a tool actually needs.
Connect an MCP server
Run local MCP servers through Warden and keep their filesystem, network, and environment access explicit.
Install
Check platform requirements for Linux, macOS, Windows, and the Docker fallback before you run.
Policy schema
Look up every policy field, validation rule, and platform-specific enforcement note.
CLI reference
Find the commands and flags for running, tracing, logging, connecting, and reviewing.
Compatibility matrix
See which tested MCP servers work, need setup, or have known limitations.
Security review
Understand what Warden enforces, what it cannot guarantee, and how to verify your own setup.