---
title: "What MCP cannot do"
url: https://docs.corefinity.com/mcp/what-mcp-cannot-do
type: page
last_updated: 2026-11-13
feature: mcp
---
# What MCP cannot do

The actions that stay with a person in the Control Panel, and the protocol features the server does not offer.

An assistant works with your rights, inside its grant. These things stay out of its reach whatever you grant it.

## Access and identity

| An assistant cannot                                             | Because                                                                              |
| --------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Do more than you can                                            | Every call is checked against your own role in the organisation.                     |
| Work for Corefinity staff, or for an account without two-factor | Those accounts are refused.                                                          |
| Create, widen or revoke a token or an app connection            | You do that in your browser, with your two-factor code.                              |
| Create a REST API token                                         | You create those on your profile: see [API tokens](/guides/your-account/api-tokens). |
| Approve its own missing scope or pin                            | It can only hand you the link.                                                       |
| Sign in with an API token or a browser session                  | The MCP server accepts MCP grants only.                                              |

## Secrets and money

| An assistant cannot                               | Because                                                |
| ------------------------------------------------- | ------------------------------------------------------ |
| See a password or login by default                | It opens in your browser: see [Secrets](/mcp/secrets). |
| Add or change a payment method, or pay an invoice | There are no tools for it.                             |

## Things only you decide

- Typing a two-factor code.
- Agreeing to a backup archive of a site you are moving from another host.

## Protocol

| Not offered                 | What happens instead                                                                   |
| --------------------------- | -------------------------------------------------------------------------------------- |
| Server-sent events          | Every request gets one JSON answer.                                                    |
| Sessions                    | Every request is authenticated on its own.                                             |
| Batched requests            | Send one request per call.                                                             |
| Pushed progress             | Poll the task: see [Long-running tasks](/mcp/long-running-tasks).                      |
| Large files inside a result | Read in pages, or use a transfer: see [Files and transfers](/mcp/files-and-transfers). |
