mcp 0.5.0 tool execution with external api calls - no timeout inheritance from agent config
we just discovered that when a tool makes an external api call, it doesn't inherit the agent-level timeout config at all. had a tool that calls stripe api with default 60s timeout, agent timeout set to 30s, tool just ignored it and kept waiting tested on mcp sdk 0.5.0, agent timeout set in config to 30000ms, tool made http request with no explicit timeout and waited full 60s before failing. anyone else hit this or know if its fixed in 0.5.1?
ok so does it inherit ANY timeout config or just ignore everything. tested this exact thing with external api tool on 0.4.2 and it at least respected parent timeout
in 0.5.0 it ignore all timeout config from agent. tool just run until completion or crash, no inherited timeout
tested same thing, tool just runs until it completes or crashes. no timeout inheritance at all. had external api tool that took 12 minutes to return and agent just waited