Skip to content

Conversation

aarora79
Copy link
Contributor

This PR addresses issue #35 by creating comprehensive documentation for the fine-grained access control system in the MCP Gateway Registry.

Created docs/scopes.md with detailed documentation covering:

  • Scope system architecture and relationship with Cognito
  • UI scopes vs server scopes differentiation
  • Methods vs tools access control explanation
  • Scope validation logic and algorithm
  • Configuration examples for different user roles
  • Security considerations and best practices
  • Troubleshooting guide for common issues

The documentation explains how the system differentiates between MCP protocol methods and specific tools, providing granular control over individual tool access. For tools/call method, the system performs additional validation to check if the specific tool name is allowed.

Closes #35

aarora79 added 2 commits June 15, 2025 18:27
…trol system

- Document scope system architecture and relationship with Cognito
- Explain UI scopes vs server scopes and their purposes
- Detail methods vs tools access control differentiation
- Provide scope validation logic explanation
- Include configuration examples for different user roles
- Add security considerations and best practices
- Include troubleshooting guide for common issues

Addresses issue #35
…tion

- Add note that FGAC concepts apply to any IdP, not just Cognito
- Clarify that group names and scope names are fully customizable by platform admins
- Emphasize consistency requirement between IdP and scopes.yml configuration
@aarora79 aarora79 merged commit c3640d9 into main Jun 15, 2025
0 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add scopes.md documentation for fine-grained access control system
1 participant