Enterprise Security & Audit — MCP in 2026
Enterprise Security & Audit
Production-ready MCP
Production MCP deployments in 2026 require security controls far beyond basic OAuth tokens. The Security Working Group has defined standards for:
Audit Logging
Every MCP interaction should be logged with:
| Field | Purpose |
|---|---|
| Timestamp | When the action occurred |
| Client ID | Which user/agent made the request |
| Server ID | Which MCP server handled it |
| Tool Called | Exact tool name and arguments |
| Result | Success/failure + truncated response |
| Token Count | Tokens consumed for billing |
Incremental Scope Consent
Instead of granting an MCP server blanket access, users can grant incremental permissions:
- First request: "Can I read your calendar?" → User approves
read:calendar - Later: "Can I create events?" → User approves
write:calendar
Each scope is granted individually via WWW-Authenticate step-up challenges (insufficient_scope), never all-or-nothing.
Discovery via .well-known (RFC 9728 & Server Cards)
Remote MCP servers expose /.well-known/oauth-protected-resource (RFC 9728) so clients discover trusted OAuth 2.1 authorization servers and required scopes upfront, alongside emerging .well-known MCP Server Cards describing capabilities and publisher identity before invoking tools.
Verify tool call telemetry and audit trail entries in the central security log.