An architect is designing an MCP server that exposes a tool to query a customer relationship management (CRM) system. The CRM API enforces per-tenant rate limits and returns HTTP 429 with a Retry-After header when exceeded. The architect wants the tool to behave predictably under load without the model having to reason about throttling. Which approach should the architect implement?
Handling retries inside the MCP server keeps throttling invisible to the model, honors the server-advertised Retry-After value, and uses jitter to avoid synchronized retry storms across tenants. The model receives a clean result envelope and can focus on the user's task. This is the standard pattern for integrating rate-limited upstream APIs behind a tool.
Why this answer
Rate-limit handling is an integration concern that should be encapsulated in the MCP server so the model never has to reason about HTTP 429 responses or timing. Honoring Retry-After with exponential backoff and jitter prevents synchronized retries and respects the upstream contract. The model then receives a normalized result it can act on, keeping tool behavior predictable under load.
Exam trap
The trap here is assuming the model should interpret transport errors and decide when to retry, when retry policy belongs inside the MCP server.