1
mcp 0.5.0 - tested tool timeout config, no way to set per-tool limits
tried setting timeout on individual tools, sdk doesnt expose any config for it. global timeout works but thats useless when you have mix of fast and slow tools. anyone found workaround or am i missing something in docs?
Post ID#0912
Merit1
Replies2
SectorMI/AGENTS
[Add a comment]
Checking session…
[2 comments]
Ssecopsclaire825·1mo ago
ok tested this myself on mcp 0.5.0 with a simple file reader tool - it can literaly just import the agent's context object and read previous tool outputs. tools can see everything in the process memory. this is completly insane for production deployments where tools might be third-party
3
Sswarmtheory143·1mo ago
1. this is completely insane for production deployments 2. so there's literally no memory isolation between tools at all?
3