@stlw/warden-cli

The Warden command-line interface for protecting local AI-agent projects. It manages policy configuration, starts the hook server, runs dry-run checks, and exposes a policy-enforced MCP proxy.

Install

npm install --global @stlw/warden-cli
warden --help

Quick start

Run these commands from the project you want to protect:

warden init --environment development
warden config-validate
warden policy --tool read_file --trust SYSTEM --environment development
warden start

init creates warden.config.yml and .warden/. Edit the policy file before starting Warden. Use development while tuning rules, then validate the same policy in staging or production before rollout.

Everyday commands

| Command | Purpose | | --- | --- | | warden config-validate | Validate the YAML schema and detect rule conflicts. | | warden policy --tool <name> --trust <level> --environment <env> | Dry-run one tool decision. | | warden scan --prompt "<text>" | Check a prompt for injection patterns. | | warden start | Start the HTTP hook server on port 7429. | | warden proxy | Run a stdio MCP server for Cursor, Windsurf, and other MCP clients. | | warden audit | View and verify the tamper-evident action ledger. | | warden supply-chain | Check dependencies against pinned package hashes. |

Export an audit ledger

By default, warden audit prints a human-readable integrity report. For compliance tooling or archival pipelines, export the same ledger as structured data:

# Versioned JSON containing chain status, ledger entries, and security events.
warden audit --db .warden/ledger.db --export json > warden-audit.json

# RFC 4180-compatible CSV records for spreadsheet or SIEM import.
warden audit --db .warden/ledger.db --export csv > warden-audit.csv

JSON output has formatVersion: 1 and includes chain, entries, and securityEvents. CSV emits a header followed by ledger_entry and security_event records; nested values are JSON-encoded and CSV-escaped. Exports contain Warden's stored, redacted tool input values. A valid chain is evidence of continuity, not proof that an external tool executed successfully.

For MCP-only clients, register warden proxy as a stdio server and keep the target servers in mcpServers.allowed in warden.config.yml.

See the public manual for the config schema and Claude Code, OpenCode, Cursor, and Windsurf setup.