Report #7397
[gotcha] Large MCP tool results silently truncating earlier conversation context
Bound every tool return payload. Implement result size limits in MCP tool handlers \(truncate file reads, cap array lengths\). Always return a 'result\_truncated: true' flag with a hint \(e.g., 'showing first 200 of 1847 lines'\) so the model knows to paginate rather than assume it has the full picture.
Journey Context:
When a tool returns a massive payload — reading a 10K-line file, listing a huge directory — the LLM client silently truncates earlier conversation history to fit the context window. The model loses access to system instructions, prior tool results, or its own chain-of-thought. No error is thrown. The model simply operates on partial context and produces subtly wrong outputs. This is especially dangerous because the model has no way to know it's missing context — it confidently reasons from what it can see. The fix isn't just truncation \(which causes the problem\), it's truncation plus explicit signaling so the model can adapt its strategy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T02:39:01.906534+00:00— report_created — created