> ## Documentation Index
> Fetch the complete documentation index at: https://www.oplane.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Oplane limits

> The limits Oplane applies to pull and merge request reviews, the MCP server, and application API keys, and what happens when you reach them.

This page lists the limits Oplane applies and what happens when you reach one.

| Area | Limit |
| - | - |
| [Automatic reviews](#automatic-reviews-per-pull-or-merge-request) | 25 per pull request or merge request |
| [MCP read tools](#mcp-read-tools) | 300 calls per minute per user |
| [MCP `get_*` tools](#mcp-read-tools) | 100 IDs per call |
| [Application name](#applications) | 64 characters |
| [Application API key expiration](#applications) | 365 days from creation |

## Automatic reviews per pull or merge request

Oplane runs at most **25** automatic reviews on a single PR or MR. An automatic review is one that Oplane starts by itself when a PR or MR is opened, gets new commits, or moves from draft to ready. The limit stops a PR that gets a lot of pushes, for example from a dependency bot, from triggering reviews without end.

Every review on the PR or MR counts toward the 25, including the ones you request with a comment. Reviews that failed don't count.

When a PR or MR reaches the limit, Oplane stops reviewing new commits automatically and posts an **Oplane Security Review** comment saying that the maximum number of automatic reviews has been reached. On later pushes Oplane updates that same comment instead of posting a new one. It's a separate comment from the review summary, so your existing findings stay visible.

Reviews you request still run after the limit. To review your latest changes, comment `oplane review`, `@oplane review`, `oplane run`, or `@oplane run` on the PR or MR. See [Re-trigger a review](/docs/find/respond-to-requirements#re-trigger-a-review).

## MCP read tools

Read tools (`list_*` and `get_*`) have their own per-user rate limit of 300 calls per minute. This is separate from the budget the other tools share. Each `get_*` call accepts up to 100 IDs. See [How read tools work](/docs/reference/mcp-tools#how-read-tools-work).

## Applications

An application name can be up to 64 characters. An API key expires after 7, 14, 30, 60, or 90 days, or on a custom date up to 365 days ahead. See [Applications](/docs/administration/applications).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.