PRACTICAL FIELD GUIDE
Distinguish 402 write caps from 429 request caps
MCPBackend quota errors identify different capacity boundaries. A write or storage cap affects mutations, while the API-request cap can block reads as well.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Read the JSON error code alongside the HTTP status.
- Compare the affected project's usage with the relevant current plan limit.
- Adjust the workload or capacity deliberately and show a useful application state instead of retrying continuously.
What this looks like
ILLUSTRATIVE EXAMPLE
A client sees quota_requests and keeps polling for recovery. Those retries cannot bypass a monthly request cap.
A boundary to keep clear
Do not tell users that reads always continue at every cap. That statement only describes write-side quota conditions.
MCPBackend context
Use get_project_api or the dashboard's generated OpenAPI contract for your project's exact data-plane routes. Machine keys and end-user tokens have different access models. Treat error status and JSON code together, keep credentials out of URLs, and test against disposable records before changing real data.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.