Limits
The request rates and sizes of the Corefinity MCP server, and where each other limit is stated.
On this page
A refused call says when to try again. A tool result carries retry_after_seconds, and an HTTP 429 carries a Retry-After header.
Requests
| Limit | Value | When it is reached |
|---|---|---|
| Requests per grant | 600 a minute | HTTP 429 rate_limited |
| Requests per organisation, all grants | 3,000 a minute | HTTP 429 rate_limited |
| Requests in flight per grant | 8 | HTTP 429 too_many_in_flight |
| Requests in flight per organisation | 24 | HTTP 429 too_many_in_flight |
| Command starts per grant and environment | 120 a minute | Tool result rate_limited |
| Changes started per organisation | 120 a minute | Tool result rate_limited |
| Requests with an unrecognised token, per IP address | 60 a minute | HTTP 429 rate_limited |
Some actions also have a budget of their own, shared with the API and the Control Panel: see Rate limits.
Sizes
| Limit | Value |
|---|---|
| Request body | 8 MiB |
Tools per tools/list page | 75 |
| Log query result returned inline | 256 KiB; a larger one arrives as a link to read |
| Command script | 256 KiB |
| Command environment variables | 64 |
| Command output returned inline, per stream | 64 KiB |
| Command output kept | 64 MiB |
Commands
| Limit | Value |
|---|---|
| Commands running per environment | 4 |
| Commands running per organisation | 50 |
Limits stated elsewhere
| Limit | Page |
|---|---|
| Token and approval lifetimes, tokens per person | Sign in and tokens |
| Pins, IP addresses and expiry of a grant | Limit a grant |
| Task polling, result lifetime and command waits | Long-running tasks |
| File, upload and archive sizes, transfer lifetimes | Files and transfers |
| Secret page links | Secrets |
Was this helpful?