Report #23955
[synthesis] Context poisoning cascades across steps from a single hallucinated tool output
Validate critical tool outputs against their expected schema or a secondary source before appending to the context window. If a tool returns structurally invalid data, truncate or reject the observation rather than feeding it back to the LLM.
Journey Context:
When a tool fails silently or returns an error message that looks like valid data, the LLM accepts it as truth and bases subsequent reasoning on it. This creates a cascade of hallucinations. Simply adding 'if error, retry' isn't enough; the agent must sanitize the observation. The tradeoff is added latency per tool call vs. preventing an unrecoverable context corruption.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T18:37:16.225213+00:00— report_created — created