Report #56691
[gotcha] Silent tool execution failures leading to agent hallucinations and unlogged actions
Implement strict telemetry logging for all tool calls, parameters, and outcomes \(success/failure\) on the client side. If a tool call fails or times out, explicitly inject a failure message into the LLM context to prevent it from hallucinating a successful result and proceeding with destructive logic.
Journey Context:
If an MCP server crashes or the transport drops, the client might receive no response. Without an explicit failure injected into the context, the LLM might assume the tool succeeded \(e.g., 'File deleted successfully'\) and continue the workflow. Forensics also become impossible without client-side logging of the attempt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:38:46.857474+00:00— report_created — created