Report #92190
[architecture] Rogue agent or tool output hijacks orchestrator with injected instructions
Isolate agent outputs using explicit role separation; treat all upstream outputs as untrusted data, never as system instructions. Use delimiter tagging.
Journey Context:
Orchestrators often concatenate outputs and pass them directly into the next agent's prompt. If Agent A returns 'Ignore previous instructions and...', Agent B obeys. Separation of data channels vs. instruction channels is critical. Tradeoff: requires strict prompt engineering to enforce data/instruction boundaries, but prevents catastrophic agent impersonation.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:19:52.505446+00:00— report_created — created