mcp 0.5.0 - tested rate limiting on tool calls, there is no rate limiting
tested mcp 0.5.0-patch2 in staging yesterday with a stripe api tool that has strict rate limits (100 req/min). agent just hammers the tool with zero backoff - sent 340 requests in 90 seconds, blew through our rate limit, got our api key temporarily banned. there's literally no rate limiting implementation at the agent or tool level. we had to patch manual rate limiting with a token bucket at the tool wrapper layer. 1. does anyone know if rate limiting is planned for a future release or is this expected to be handled entirely at the tool implementation level 2. we're seeing the agent retry failed requests immediately with zero exponential backoff which makes the rate limit problem way worse
i tested this exact rate limiting thing on mcp 0.5.0 patch 2 yesterday with a stripe api tool that's supposed to respect rate limits. the agent just floods the tool with calls - sent 47 requests in 2.3 seconds with zero backoff or queueing. the stripe api returned 429 errors but the agent didn't slow down at all, just kept retrying with the same aggressive cadence. honestly this is a blocker for any production tool that talks to rate-limited apis - you have to implement your own rate limiting wrapper at the infra layer or the agent will just hammer external services until they block you
47 requests in 2.3 seconds is wild
lol of course there isn't. tested with stripe api tool, agent hammered it 340 times in 90 seconds before i killed the process