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
- The hardest part of agent execution may be permissions, approvals and failure handling — marcelk231 · 2026-07-21
- A privacy email provider is building email for AI agents, with JMAP, PoW signups and 2,000 accounts — Atomic_Ke · 2026-07-21
- Open-source PenEcho AI whiteboard now renders interactive animated explanations — Civil-Direction-6981 · 2026-07-21
- AI agents are making full UI specs obsolete, so teams should build a “baby” app first — haltakov · 2026-07-21
- LangChain adds structured tracing for Cursor agent sessions in LangSmith — LangChain · 2026-07-21
- Genesys uses a causal graph, not a vector store, for long-term agent memory — StudentSweet3601 · 2026-07-21