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

# MCP Security

> How the Statisfy MCP server keeps AI assistants within your role: keyless sign-in, per-request role and product checks, consent for changes, an audit log of every change, and usage limits.

The Statisfy MCP server is built so that an AI assistant can never do more than the person who connected it, and every change can be traced.

## Controls

| Control | How it works |
| - | - |
| **Standard, keyless sign-in** | You connect through OAuth 2.1 with PKCE, from inside your AI assistant. There are no API keys to copy, paste, or share. |
| **Keys never stored in the clear** | Statisfy keeps only a salted hash of each connection's key. A key can't be read back, even by Statisfy. |
| **One person, one workspace** | Each connection acts for the person who authorized it, in one workspace. It never crosses workspaces. |
| **Your role, checked on every request** | Each request is checked against your Statisfy role at that moment. A role change applies within minutes, and leaving the workspace stops your connections. See [Roles and permissions](https://help.statisfy.com/mcp/roles_and_permissions.md). |
| **Your products, checked on every request** | Claude reaches only the parts of Statisfy your workspace has. |
| **Changes only with your consent** | A connection can make changes only if you ticked **Make changes** when you connected it. Without it, the tools that make changes don't appear at all. |
| **Approval before changes, if you want it** | Statisfy marks every tool that changes data. In Claude's connector settings, set the write/delete tools to **Needs approval** and Claude asks you before every change. |
| **Read-only roles stay read only** | A Viewer can't make changes, whatever the connection allows. |
| **Sensitive actions stay with admins** | Deleting records, changing workspace setup, publishing, enabling automations, activating digital workers, and reading the audit log need the Admin role. |
| **Every change audited** | Each change, including refused attempts, is in [Settings → Audit logs](https://help.statisfy.com/admin/audit_logs.md) under the person's name. So is each new connection. |
| **One active connection per app** | Connecting an app again replaces your earlier connection for it, so stale keys don't pile up. |
| **Instant disconnect** | Admins can disconnect any connection in [Settings → MCP Connections](https://help.statisfy.com/mcp/managing_connections.md), and it stops immediately. |
| **Connections expire** | Each connection expires after 180 days. Its owner connects again to keep using it. |
| **Usage limits** | Each person and each workspace has a cap on reads and changes per minute. See [Usage limits](#usage-limits). |
| **Encrypted in transit** | All MCP traffic uses HTTPS with TLS 1.2 or later, and plain HTTP is redirected to HTTPS. When you sign in, Statisfy sends you back only to an `https://` address the app registered, matched exactly. |

## Every change is recorded

Every change made through MCP is recorded in the audit log, under the name of the person whose connection made it. Admins see it in **Settings → Audit logs**. Set **Surface** to **MCP** to see only changes made through MCP connections.

![Settings → Audit logs filtered to the MCP surface, showing contact creates and updates with the fields that changed, and an update refused with status 403](https://cdn.statisfy.com/help-artifacts/admin/mcp-audit-logs-mcp-surface.png)

Each row shows the time, the person, the **MCP** surface, the record that changed, the action, and the fields that changed. A refused or failed attempt carries its status, such as **403**, and shows **Failed: nothing stored**. Connecting, and replacing an earlier connection, are recorded too, under the object **Mcp connection**. For everything the audit log records and how to filter it, see [Audit logs](https://help.statisfy.com/admin/audit_logs.md).

> [!NOTE]
>
> The audit log records changes. Questions Claude answers by reading your data aren't recorded there.

## Usage limits

To keep your workspace responsive, each person's MCP connections can make up to 300 reads and 60 changes per minute through the tools that work across Statisfy. Your workspace as a whole can make up to 1,200 reads and 240 changes per minute. If Claude goes over, Statisfy tells it to slow down, and it can try again a moment later.

For Statisfy's wider security practices, see [Security](https://help.statisfy.com/resources/security.md).


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