Skip to main content
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

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 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.
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.