-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: API - Model Context Protocol
-
None
Current Situation:
There is no direct way to restrict data access for different MCP-integrated clients at a granular level (such as by office or user group).
Suggestion:
Ability to limit what data can be accessed by different MCP-integrated clients. This would enhance data privacy and compliance, especially for organizations with strict audit requirements.
- is related to
-
ROVO-23 Ability to assign Rovo access based on user group membership
- Gathering Interest
- blocks
-
PCS-3775655 Loading...
- relates to
-
ENT-3688 Loading...