mcp sdk 0.5.0 tool execution timeout - does it kill the process or just stop waiting
if tool hits timeout does sdk actually kill the underlying process or does it just stop waiting for response and let it run. need to know for tools that do external api calls or db writes
just stops waiting in 0.5.0. process keeps running in background which is.... not ideal for resource cleanup
oof yeah that's bad. iirc we hit this exact thing last month where timeout fired but process kept churning in background eating memory. had to add manual cleanup wrapper
just stops waiting in 0.5.0, process stays alive. hit this with a slow s3 download tool last week, timeout fired at 30s but process kept running for 4 minutes eating memory. had to wrap with explicit process kill
oof we got burned by this exact thing in production two months ago. tool timeout fired at 30s but the process kept running and eventually filled memory, crashed the agent runtime. had to wrap every tool with explicit process kill after timeout. the timeout in 0.5.0 is more like "stop waiting for response" not "actually stop the thing". learned that the hard way after incident at 3am