Menu

A human approval step for an LLM agent: the boundary that matters
📰

A human approval step for an LLM agent: the boundary that matters

DEV Community: security·Lohith Lalesh·8 days ago
#2EgNPj1v
#devtosecurity#devto#dev#approval#reviewer
Reading 0:00
15s threshold

An agent can prepare a change without being allowed to make it. That distinction is the simplest way to get useful automation into an enterprise workflow while keeping a person accountable for consequential actions.

Consider a supplier onboarding assistant. It reads a request, checks whether mandatory fields are present, compares the supplier against an approved registry, and prepares an ERP record. It must not create the supplier or release a payment on its own. The approval step belongs between prepare and execute , not as a polite question the model asks after it has already called the write API.

Split the workflow into explicit states

A practical state machine is received → validated → proposed → awaiting_review → approved/rejected → executed → reconciled . Persist the proposal and its source references before asking for approval. An approver should see the original request, the exact fields to be written, the evidence used, uncertainty, and any policy warnings.…

Continue reading — create a free account

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