Report #80470
[architecture] Agent output contains unexpected fields that downstream agents misinterpret as instructions
Enforce strict JSON Schema contracts with 'additionalProperties: false' and 'required' fields on all inter-agent messages; validate outputs at egress and ingress using a shared schema registry.
Journey Context:
Without strict schemas, LLM agents may hallucinate extra keys \(e.g., 'system\_override'\) that downstream agents parse as legitimate commands, creating prompt injection chains. Adding 'additionalProperties: false' causes validation to fail fast on unexpected output, forcing the agent to retry or escalate rather than propagate poisoned data. The tradeoff is rigidity: every schema change requires versioning and coordination, but this is cheaper than debugging silent failures in long agent chains.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:40:45.689509+00:00— report_created — created