AgentInterdict
Blog · 2026-09-09

Why Your Agent Needs Provenance Tracking

The scariest agent attacks aren't the agent going rogue. They're a poisoned document quietly steering a legitimate action. Provenance is how you catch that.

Most people think the dangerous agent failure is the agent doing something obviously insane. It's not. The dangerous failure is the agent taking a perfectly reasonable action, but for the wrong reason, because the content that influenced it was poisoned.

That's where provenance comes in. Provenance means tracking where every piece of content that influenced an action came from. Which document? Which memory? Which retrieved source? If you can't answer that, you can't audit the action after the fact, and you can't tell a legitimate action from a steered one.

The rule that makes provenance useful: derived content can never outrank its source. If a memory was written from an untrusted document, it carries that untrusted origin with it, and it can't gain authority it never had. That single rule stops the 'poisoned memory looks legitimate' attack dead.

Without provenance, you're flying blind. With it, you can trace every action back to its origin and decide whether that origin was allowed to influence it. That's the difference between hoping and knowing.

Retrieval ≠ Permission

Reading content is not the same as authorising it to act. The boundary is where security actually happens.