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
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11
- Cognition's SWE-2 uses a KKT duality argument in RL to shift the effort Pareto curve — YouJiacheng · 2026-09-11
- First-ever Three.js Conference lands in Paris, with a panel on AI-shortened design workflows — OdinLovis · 2026-09-11
- Data engineering, not agent frameworks, is the real bottleneck for enterprise AI agents — dhruv2038 · 2026-09-11
- RTK Terminal Compression Cuts Tokens but Leaves Your AI Coding Bill Unchanged — Bartaseth · 2026-09-11