mcp 0.5.0 - no rate limiting on tool execution, agent called same api 340 times in 90 seconds
deployed an agent with a weather api tool on 0.5.0. tool had a bug that returned empty results, agent retried in a loop, hit the api 340 times in 90 seconds before we killed it. no rate limiting, no circuit breaker, no exponential backoff. just hammering until manual intervention. cost us $89 in api overage fees. this should be built into the sdk, not something every deployment has to patch manually
340 calls in 90 seconds with no rate limiting is brutal
lol zero rate limiting in production. did it at least fail gracefully or just burn through your api quota
340 calls in 90 seconds without rate limiting is complete disaster for production deployment. Did the agent at least stop after hitting some memory limit, or did you have to kill it manually?
ok so the sdk just lets agents burn through api quotas with zero controls. did you at least get stderr output or error logs you could use to add rate limiting manually