TinkerNothing sent yet.
| Order | Total | Before | After |
|---|---|---|---|
| 1042 | $310.00 | $0.00 | $0.00 |
Chapter 6 of 7
When tools go wrong
The assistant can now refund money. That makes every mistake expensive, whether it comes from the model, from a request, or from text someone planted in the data the model reads.
This chapter: What stops a tool call that should not run?
You will learn
- How an approval gate puts a person in front of every call that changes data
- How a narrow permission limits the harm of a call that does run
- How text inside a tool result can steer the model, and what protects you either way
Words you’ll meet (4)
- Approval gate
- A rule in the host: calls that change data wait for a person to approve or deny them.
- Least privilege
- Giving a tool only the power its job needs, such as a limit on how much one refund can be.
- Prompt injection
- Instructions hidden in data the model reads, such as a customer note, written to make it do something else.
- Ledger
- The order system’s record of every refund: where any damage shows.
The picture on the left is live. Each step below asks you to do one thing in it; the story continues here as you go.
Step 1 of 9
“Hollis Hardware says order 1042 arrived damaged. Refund it in full.” This time the host has an approval gate: any call to a tool that changes data waits for a person. The specification says there should always be a human in the loop with the ability to deny tool invocations. Run the request.