Report #6265
[gotcha] Massive tool return values silently truncate conversation history on next turn
Enforce strict size limits on MCP tool return payloads \(e.g., max 10k tokens\) and implement summarization or truncation logic \*before\* appending the tool result to the context.
Journey Context:
A common failure mode is a tool \(like a file reader or SQL executor\) returning 100k tokens of data. The MCP client receives it fine, but when it injects it into the LLM context for the next reasoning step, the orchestrator silently truncates the \*oldest\* messages \(including the original system prompt or user instructions\) to fit the tool result. The agent then proceeds without its core instructions, leading to completely unpredictable behavior.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T23:40:35.053764+00:00— report_created — created