New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Your agent can already call the tool that issues a refund, and nobody decided whether it should do that on its own.
What you'll have at the end
A short list of tool calls that pause for a person's yes before running, with everything else left to run on its own
You need
A tool-using agent already wired to at least one tool that deletes something, sends something outside your system, or moves money, with every call currently running the moment the model decides to make it.
Not covered
Narrowing which tools or credentials the agent holds in the first place; this recipe assumes the tool list is already the right size and decides only which of those calls need a person's yes before running.
Leans on
Shrink an agent's blast radius by scoping down its tools
Narrow the credential and tool list to what the job needs first; a gate in front of an action the agent should never have been able to reach at all is the weaker fix.
Log every tool call so you can find what broke a run
If every call needs a record, not only the gated ones, this covers logging the whole run rather than just the approval decisions.
Give a runaway agent a spending cap
If the worry is a stuck loop burning through budget rather than one destructive call, a spending cap addresses that directly, without waiting on a person for every step.
Checked 15 Aug 2026
Part of the AI Agents cookbook