Zoho MCP Platform Security
| Control | Details |
|---|---|
| Authentication | OAuth 2.1 with two-layer consent (MCP account + service-level) |
| Unique Server URL | Each MCP server gets a cryptographically unique URL; treat as a secret |
| API Key Rotation | Immediate revocation and regeneration via UI |
| Permission scoping | Agents operate under invoking user's RBAC; no privilege escalation |
| Enterprise-grade protocols | Encrypted data handling, access controls (Zoho MCP product page) |
| Audit trails | All tool invocations logged (documented in Billing; applies platform-wide) |
| Connection management | Super Admin can share org-wide tokens OR enforce per-user auth |
Authorization Modes Comparison
| On-Demand (per-user) | Via Connection (org-wide) | |
|---|---|---|
| Who authenticates | Each user individually | Super Admin sets up once |
| Applies to | Zoho products (default) | Third-party services |
| Revocation | Per-user revoke | Admin-controlled |
| Use case | User-specific data boundaries | Shared service accounts |
MCP-Specific Governance Risks (Industry Context)
Industry security research notes that MCP OAuth governance introduces two-layer consent complexity and "shadow MCP" risks if unvetted servers proliferate (Nudge Security, Feb 2026; Obot AI, Apr 2026). Zoho's centralized console and admin-controlled Connections feature mitigate this somewhat by providing a single configuration point and organizational token management. Best practices:
- Restrict tool selection to only what is needed for each task
- Use Authorization on Demand for sensitive data (user-scoped)
- Regularly audit MCP Logs (ZUID, Execution ID) for anomalous activity
- Rotate API keys if Server URL is suspected compromised
- Use Zoho's sandbox environment for testing before production deployment