Day 9 of 1460 minExploit ArchitectHands-on lab
Day 9: Agents, Tools and Retrieval as a Privilege Path
Taught by Mr Elite Updated
By the end of today you can
- Trace how retrieved text becomes a privileged tool call in an agent
- Explain a confused deputy caused by shared credentials
- Spot backend sinks such as text-to-SQL behind a RAG front end
- Write the missing control and enforce it outside the model
So far we have attacked what the retrieval step returns. Today we look at what happens next. A RAG assistant that only answers questions can embarrass a company. A RAG assistant that can call tools can move money, run queries and send email, and it does that with credentials the user never had.
The pattern is simple. Text comes back from the vector store, the model reads it as if it were guidance, and the model asks a tool to act. If nothing outside the model checks that request, the document author has just borrowed the agent's privileges. I want you to see that happen on your own machine, then in the lab, and then name the control that should have stopped it.
In this lesson
- The idea: retrieval is a privilege path
- Watch me do it: a local confused deputy
- Backend sinks: text-to-SQL and friends
- Policy belongs outside the model
- Your turn: the confused deputy lab
Premium course
$27 one-time, lifetime access
This day is part of the full course. Unlock it to read every lesson, do every mission and track your progress to the end.
Privileged members get every paid course included. See the plans