Report #96891
[architecture] Passing full conversation histories between specialized agents leaks system prompts and enables privilege escalation
Implement a 'Principle of Least Privilege' for context. The orchestrator should construct a minimal, scoped context for the downstream agent, containing only the specific data payload required for that step, rather than forwarding the entire historical message array.
Journey Context:
It is tempting to pass the full messages array from Agent A to Agent B to preserve context. This is an anti-pattern. Agent A might have had access to a database lookup tool; if its system prompt and tool definitions are passed to Agent B, Agent B might attempt to use those tools \(which it lacks permissions for\) or extract sensitive data from the history. Stripping the context to just the structured output contract ensures security and drastically reduces token costs.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:12:53.883502+00:00— report_created — created