Authentication & scoping
- Org-scoped keys. Every
ecn_mcp_…key is tied to exactly one organization. A key for org A can never read or write org B’s data — cross-tenant access is rejected. - Hashed at rest. Keys are stored as SHA-256 hashes; the plaintext secret is shown only once at creation. If you lose it, create a new key.
- Revocable. Revoke any key instantly in Settings → Connect external AI tools
or via
DELETE /api/v1/mcp/keys/<id>/. Each key trackslast_used_at.
Reads are safe; sends are gated
ECN follows a read/write safety model:
Most AI-authored content — Context Pack edits and the outreach/GTM pipelines — enters
as
seeded/draft and is never auto-marked verified, so a person stays in the
loop before it’s published. The exception is direct-send tools like compose_email,
which send the moment they’re called — only expose them to trusted callers.
What an MCP client can and cannot do
- ✅ Search and read directory + context, manage CRM records, run prospecting, draft outreach, check spend.
- ⛔ Bypass credit budgets, escape org scoping, or read another organization’s data.
compose_email does send directly — it is not gated behind a draft.)