Connect an AI agent (MCP) — The security model

The key is the credential: anyone holding it reads this workspace as the acts-as member, so treat it like a password. Everything else follows from the acts-as design: • Permissions are the person's own. Hidden fields stay hidden, no-access tables stay invisible, and there is no separate “integration permissions” model to configure or get wrong. • Revoke on the Developers page. The key stops answering within a minute everywhere. Removing the member from the workspace kills their connections too. • Requests are rate-limited per key, and CSV exports write to the workspace audit trail like any other export. • Trial and billing apply. A workspace whose trial has ended answers MCP requests with a payment-required error, the same rule as the REST API. The connection acts as a person, so every permission already set up in RowFold applies — there is no second set of rules to keep in step.