CorefinityCorefinityDocs
Open the Control PanelControl Panel
Essentials · 11 of 16

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

LimitValueWhen it is reached
Requests per grant600 a minuteHTTP 429 rate_limited
Requests per organisation, all grants3,000 a minuteHTTP 429 rate_limited
Requests in flight per grant8HTTP 429 too_many_in_flight
Requests in flight per organisation24HTTP 429 too_many_in_flight
Command starts per grant and environment120 a minuteTool result rate_limited
Changes started per organisation120 a minuteTool result rate_limited
Requests with an unrecognised token, per IP address60 a minuteHTTP 429 rate_limited

Some actions also have a budget of their own, shared with the API and the Control Panel: see Rate limits.

Sizes

LimitValue
Request body8 MiB
Tools per tools/list page75
Log query result returned inline256 KiB; a larger one arrives as a link to read
Command script256 KiB
Command environment variables64
Command output returned inline, per stream64 KiB
Command output kept64 MiB

Commands

LimitValue
Commands running per environment4
Commands running per organisation50

Limits stated elsewhere

LimitPage
Token and approval lifetimes, tokens per personSign in and tokens
Pins, IP addresses and expiry of a grantLimit a grant
Task polling, result lifetime and command waitsLong-running tasks
File, upload and archive sizes, transfer lifetimesFiles and transfers
Secret page linksSecrets
Was this helpful?
Open in ClaudeOpen in ChatGPT