Operations
Human-in-the-Loop for AI Agents, Without the Bottleneck
Full autonomy is reckless, approving everything is unusable. How to risk-tier agent actions and design approvals that take seconds, not meetings.
Full autonomy is reckless and approving everything is unusable. The teams that get value from agents put a human in the loop for exactly the actions that deserve one.
The autonomy trade-off
Give an agent free rein and one hallucinated parameter becomes a deleted database or a mass email. Gate every step and you have hired a very slow intern you have to babysit. Neither extreme survives contact with production.
The way out is boring and effective: classify actions by blast radius, automate the reversible ones, and require a human decision for the rest.
Risk-tier your actions
Auto-approve: reads, searches, drafts, anything sandboxed — mistakes cost nothing. Notify: low-stakes writes you want visibility on, like creating tickets or internal notes. Require approval: money movement, deletions, credential use, anything sent to an external human — payments, outbound email, publishing. Never allow: actions with no legitimate agent use case in your setup. A blocklist is a policy too.
Make approving take five seconds
Approvals fail when they are slow or vague. The request must arrive where the human already is — their phone — and carry enough context to decide instantly: what the agent wants to do, to whom, with which parameters, and why.
Staleness matters as much as speed. An approval granted for a request from an hour ago may no longer describe reality. AgentLock auto-blocks any request that is not approved within five minutes: unanswered means no.
Policies cut the noise
If your phone buzzes forty times a day, you will start rubber-stamping — and the control is theatre. Push routine cases into policy: allowlisted recipients, spending thresholds, rate limits, time windows. The human should only see the requests where judgement genuinely adds something.
Close the loop with a record
Every request, approval, denial and timeout belongs in an audit trail — who approved what, when, with which parameters. That is how you tune policies over time, and how you answer "what happened?" with facts instead of vibes.
More articles
Security
How to Keep API Keys Out of Your AI Agents' Hands
Every key an AI agent can read is a key it can leak. Why credentials don't belong in prompts or agent environments — and how the gateway pattern fixes it.
Read article →
Compliance
AI Agent Audit Trails: What to Log, a Template and the EU AI Act
What an AI agent audit trail must record, a record template to copy, the logging duty in Article 12 of the EU AI Act — and three examples from practice.
Read article →
