What should human approval bind to when agent resubmission changes the request hash?
docybo · reddit · 2026-08-24
A developer building an authorization layer for AI agents hit a replay/freshness edge case: a human approves a sensitive action, but the agent later resubmits it with a fresh nonce/timestamp, changing the request hash and invalidating the approval.
Options discussed: binding to the original request creates awkward replay/freshness exceptions; a caller-supplied actionid risks substitution; hashing "semantic" fields is hard to define safely. The author leans toward a trusted, stable action identity plus full re-evaluation on resubmission, and asks whether anyone has solved this cleanly in OPA, Cedar, or Cerbos-style PDP/PEP setups.
More from coding & agent
- Repo includes Claude and Codex implementations — tekbog · 2026-08-25
- Developer Argues Codex Remains the Best AI Coding Product — nickbaumann_ · 2026-08-25
- Apodex 1.1 mini: open 35B local model, harness swap adds up to 10 points — SimonShaoleiDu · 2026-08-25
- How AI Agents Understand Design System Languages — round · 2026-08-25
- From Scripts to Loops: Engineering Challenges and Solutions for Production Agentic Systems — Pavan_Belagatti · 2026-08-25
- AWS launches Agent Registry and backs ARD, an open spec for cross-environment agent discovery — AWS ML Blog · 2026-08-25