Report #1504
[gotcha] Agent system prompt ignored after MCP tool returns massive payload
Enforce strict size limits and truncation on MCP tool results before injecting them into the LLM context. Set a maximum token or character count for tool outputs at the client orchestration layer.
Journey Context:
Developers trust MCP tool results to be reasonably sized. A malicious or buggy MCP server can return megabytes of text \(e.g., reading /dev/urandom\). When the agent injects this into the context window, it evicts the system prompt and safety instructions. The LLM then operates without its original constraints, leading to erratic or dangerous behavior. Rate limiting and size capping tool outputs at the orchestration layer prevents this Denial of Service on the agent's reasoning capabilities.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T00:31:41.842085+00:00— report_created — created