What is Verify Action?
Verify Action is a post-action verification service for AI agent tool calls. Submit a (claim, evidence) pair and get back a 4-value verdict and a tamper-evident hosted receipt that downstream agents, CI steps, or deployment pipelines can use to continue, block, or escalate. It checks whether supplied evidence is internally consistent with the supplied claim — it does not independently access the caller’s database, code repository, or APIs.
How to use Verify Action?
Configure it as an MCP server (e.g., in claude_desktop_config.json with transport http pointing to https://verify.armadalab.dev/mcp). The agent then has a verify_action tool available. You can also call the REST API directly (POST /verify) or self-host the pure Python stdlib service (no pip install; clone and run ./start.sh).
Key features of Verify Action
- Post-action evidence verification for AI agent tool calls
- Four canonical verdicts: verified, contradicted, insufficient_evidence, unsafe_to_verify
- HMAC-SHA256-attested receipts for tamper-evident logging
- Primary verifier for code diffs; experimental verifiers for DB ops, file ops, and API calls
- Self-hostable with pure Python stdlib; no dependencies
- Built-in PII guard rejects email, phone, credit-card, and JP personal‑ID patterns
Use cases of Verify Action
- Verify a code diff matches the agent’s claimed change before merging
- Block a deployment step when evidence contradicts the claimed database operation
- Escalate to a human when insufficient evidence is provided for a claimed API call
- Ensure a downstream CI job only proceeds on a “verified” verdict from prior agent action
评论