Security and data
How sign-in works, what Covenant MCP can see, what leaves Covenant, and how to turn it off.
Sign-in
- OAuth 2.1 with your Covenant login. Each person signs in on Covenant's own sign-in page (
signin.covenant.co, or your firm's Covenant domain). Your AI tool never sees a password and Covenant issues no shared keys. - One organization per connection. If you belong to more than one Covenant organization, you pick one at sign-in, and the connection asks about that one only. To switch, disconnect and connect again.
- Tokens are for this server only. Every request carries a short-lived access token. Covenant checks its signature, issuer, audience and expiry on every call, and refuses a token issued for any other server.
- Impersonated and reviewer-preview sessions are refused. Only a person signed in as themselves can use Covenant MCP.
What Covenant MCP can see
- Exactly what you see in Covenant. The server applies the same organization, role and strategy permissions as the Covenant app, on every call. A fund you cannot open in the app does not exist to it.
- Released work only. A review still in progress at Covenant is not visible until it is released.
- Read-only. Every tool is marked read-only. Nothing Covenant MCP does changes your data.
- Answers, not documents. Tools return Covenant's surveyed terms, summaries, citations and amendment changes. They do not return the full text of your documents.
What leaves Covenant
- Only the answer to the question asked. A question about one fund returns that fund's answer, nothing about other funds, other people or other firms.
- To your own AI account. The answer goes to the Claude, ChatGPT or Copilot account your firm chose, under your firm's agreement with that vendor. Covenant shares nothing with those vendors on its own.
- Covenant keeps no copy of the conversation. The conversation lives in your AI tool.
See the Covenant MCP privacy policy for the full statement.
Audit and limits
- Every call is logged. Each tool call is recorded against the person and the AI tool that made it, in the same audit trail as the Covenant app.
- Rate limit. 30 requests per minute per person. Over the limit, the server answers "Too many requests" until the minute passes.
- Time limit. A question to
ask_covenanthas four minutes to finish. A slower question returns a message asking for a narrower one.
Turning it off
| Who | How | Effect |
|---|---|---|
| Your firm | Ask support@covenant.co | Covenant switches MCP off for the whole organization. The next call from anyone is refused. |
| A person | Disconnect Covenant in their AI tool | Their tool stops calling Covenant. |
| Covenant | Revoke the person's access at sign-in | Their tool cannot refresh its token and must sign in again. |
Network
Requests to Covenant MCP come from your AI vendor's servers, not from your network. If your firm restricts outbound traffic from the AI tool, allow covenant.co (or your Covenant domain) and signin.covenant.co.