Menu

1 / 3

Letting an AI agent act, but not alone: designing human approval steps for agent tool calls

DEV Community: security·Sushil Barwal·11 days ago
#H9DA8fGO
#devtosecurity#devto#dev#damaged#agent
Reading 0:00
15s threshold

Most AI agent demos end at the moment the agent decides to do something: send the email, refund the order, update the CRM record. In a real business, that moment is where the engineering starts. The question a client asks us most often after "can it do this?" is "what stops it doing the wrong thing?"

This post is the pattern we use when we build agents for small and mid-sized businesses in the USA, UK, Canada and Australia: sort every tool the agent can call by risk, and put a person in front of the risky ones. The examples use n8n because it has human review built into its AI agent tooling, but the design works in any framework.

Step 1: list every tool and give it a risk level

An agent is only as dangerous as the tools you give it. Before writing a prompt, write a table:

Tool What it changes Who sees the result Can it be undone?…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.