Author Questions Whether Agent Approval Is Just a Formality
Street_Inevitable_77 · reddit · 2026-07-18
The author built a multi-tenant MCP server with a write path, allowing agents to perform real financial operations, with an outer 'human approval / draft-then-commit' process.
He argues that many so-called human approvals are essentially just treating the model's summary as fact and clicking confirm, making it a mere 'agree button' rather than a real security layer. The author proposes three key conditions:
- The approval interface must show the real diff, not a model-generated paraphrased summary.
- The approval step should be outside the tool call; the model cannot trigger the commit itself.
- Rejection must be cheap enough; otherwise, users will just approve to save effort.
The author ends by asking: does your agent's write approval process truly show original changes and allow low-cost rejection, or is it still just a summary and a button?
Related event: Author Says Agent Human Approval Is Often Theater(2 posts)→
More from coding & agent
- Reticle builds a verification layer that lets AI coding agents check their own generated code — Scobleizer · 2026-10-27
- Trust your agent, but read its logs: Claude managed agents tips — brada · 2026-10-27
- Dev training a guard model to block prompt injection, tool and memory poisoning — gnukeith · 2026-10-27
- Dev trains a ~4GB-VRAM sentinel model to guard against prompt injection and poisoned memory — gnukeith · 2026-10-27
- Superset rebrands as Paradev, raises $11.5M seed led by USV — massimosgrelli · 2026-10-27
- Ex-Big Tech managers may thrive in the AI era: manage agents like you managed teams — lxfater · 2026-10-27