Skip to main content

RBAC And Audit

Use this guide to define role boundaries and audit expectations for Management MCP.

Role model​

RoleTypical MCP scopeRecommended usage
viewertools/list, read-only tool callsdashboards, inventory sync, read bots
modifiersafe create/update operationsCI automation with approval gates
auditorread-only + audit inspectioncompliance and change review
admindestructive/high-impact toolsisolated identities only

Separation of duties checklist​

  1. Keep read automation and write automation on separate identities.
  2. Keep admin tools off default automation identities.
  3. Use explicit change windows for mutation tools.
  4. Require audit review for destructive operations.

Audit evidence to capture​

  • Actor identity (subject + role)
  • JSON-RPC method/tool name
  • Target object (collection/proxy/workflow)
  • Result status (allowed/denied/succeeded/failed)
  • Timestamp and request/session correlation

Validation tests​

  1. viewer identity attempts mutation -> expect 403.
  2. modifier performs approved update -> expect success + audit entry.
  3. Missing auth -> expect 401.
  4. Out-of-scope admin action by non-admin identity -> expect 403.