Report #65426
[synthesis] Context poisoning cascades across multiple agent steps
Quarantine untrusted tool outputs by validating them against a schema or expected state before appending to the main context trajectory. If validation fails, intercept and return a sanitized error.
Journey Context:
A single hallucinated or malformed tool output \(e.g., a bash error that includes filesystem paths\) gets injected into the agent's context. Because LLMs are strongly influenced by prior context, the agent then uses this poisoned fact to make subsequent decisions, leading to a cascade of confidently wrong tool calls. Standard RAG or truncation doesn't fix this because the damage is done by the structure of the error. Quarantining and validating tool outputs breaks the cascade by ensuring the agent's trajectory only contains verified state transitions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T16:18:08.381755+00:00— report_created — created