AI connection limits
These limits keep connected AI clients responsive and protect your work when a client makes too many requests. They apply to Vesta’s MCP connection at mcp.vesta-mcda.com.
Current limits
| Activity | Limit |
|---|---|
| All requests from your account, including the app | 240 per minute |
| MCP requests from one connection | 120 per minute |
| Read tool calls from one connection | 90 per minute |
| Preview tool calls from one connection | 30 per minute |
| Write tool calls from one connection | 30 per minute |
| MCP write attempts from your account | 500 per UTC day |
| MCP project creation attempts from your account | 6 per UTC day |
| Projects you own on the free plan | 3 total |
A connection is one AI client you approved. Connecting another client or reconnecting does not reset account limits. Project limits still apply when a project is created through AI.
What counts
Reading a model, alternatives or results counts as a read. Reviewing proposed criteria, weights or a new project counts as a preview. Saving evaluations, applying criteria or weights, and creating a project count as writes.
Every write attempt that reaches the tool budget counts, including a retry or a request that fails validation. A project creation attempt also counts toward the creation limit. Listings and other MCP messages count toward the overall request limits. Limits reset at the next minute boundary or at 00:00 UTC for daily limits.
Vesta also applies network and service-wide defenses to login, client registration and MCP traffic. Their thresholds are not published and may change during an incident.
When a request is paused
If you reach a limit, the client receives HTTP 429 and a Retry-After value in seconds. Wait at least that long before trying again. A busy service or a temporary pause may return HTTP 503 with a retry time. During a write pause, you can still read and preview projects within their usual limits.
Vesta rejects a limited request before running its tool, so that request makes no project change. If a previous write had an uncertain result, check the project before retrying. For the same intended write, reuse its original requestId and identical input; Vesta’s write receipts prevent a second change from that retry.
Your existing project permissions, consent and account controls still apply. You can review or disconnect AI clients in your profile.
See Connect AI for setup and access choices.