Report #57202
[gotcha] Agent hangs indefinitely when calling a slow MCP tool
Define explicit timeouts for tool execution on the client/host side, and for long-running tasks, implement an asynchronous polling pattern \(e.g., tool returns a task\_id, and a separate check\_task\_status tool is used to poll\).
Journey Context:
Some operations \(like running a test suite or deploying infrastructure\) take minutes. The MCP spec assumes synchronous request/response. If a tool takes 5 minutes to respond, the LLM agent's execution thread blocks, or it hits a default HTTP timeout and crashes. By returning a task\_id immediately, the tool unblocks the agent, allowing it to poll for results when ready, preventing timeout failures and wasted compute.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T02:30:00.675993+00:00— report_created — created