Part 8 of 13 · 1 min read
How to build it so it holds up
- Treat every tool result and retrieved document as untrusted data, including from internal systems that ingest outside text.
- Break the trifecta by construction: drop one of untrusted input, private data or external action per session.
- Gate the dangerous call, not the text: enforce policy on tool calls in code, outside the model.
- Use quarantine for untrusted text: typed outputs only; no free text to the privileged planner.
- Constrain egress: allowlist outbound domains and recipients; disable markdown image or link rendering of untrusted URLs where it can leak data.
- Keep filters as a layer, not the wall, and measure them on paraphrased and obfuscated attacks, not only plain ones.
- Least privilege (module 2) and human approval for irreversible actions (module 5).
- Test continuously with an attack suite (module 8) in the CI gate (Level 9 module 7).
- Log tool calls with provenance, so you can see which untrusted source preceded each action (Level 9 module 8).