Add a human breakpoint to your AI SRE agent workflow before it acts

Reaching a tool and being allowed to use it are two separate lists in the config. Put the mutable Kubernetes tools on the second one and each call pauses.

Learn more about AURA → https://www.mezmo.com/aura
Get started today → https://github.com/mezmo/aura
Get deployment help → https://www.mezmo.com/contact

A walkthrough of human breakpoints: the mechanism that lets an agent read freely while requiring a named human decision before it changes anything. The config lists which Kubernetes MCP tools the agent can reach, then separately lists the mutable ones that pause for approval. Because the root is conversational, the approval surfaces in the attended session with the exact tool name, pod, namespace, and arguments visible before anything runs. The same pod deletion is then run twice: denied once, with a re-list proving both original UIDs survive, and approved once, with a read-only call confirming the replacement.

AURA is built for SREs and platform engineers who want an agent operating in production without unsupervised write access to it.

0:00 What a human breakpoint is, and the agent's cluster tools

0:24 The MCP filter and the breakpoint list

0:47 Where the approval appears in an attended session

1:04 Demo: a read-only call runs uninterrupted

1:39 Denying a pods_delete call and verifying nothing changed

2:29 Approving the same call

3:05 Reads, denials, and approvals end to end

#HumanInTheLoop #AISREAgent #PlatformEngineering