Restrict user access to Gainsight MCP

I would like to insist on this important idea from ​@mightylud .

The initial doc says that any registered user can access the MCP server for search only.

The range of fields that the MCP includes is limited by the API itself, if I understand this correctly. I am assuming that moving forward, the MCP server will have access to more data…

This generates some concerns in my org. Gainsight assumes on our behalf that it is desirable for us to open the gates for any reg user. However, we would like to control the access and possibly restrict what is visible to registered members through the MCP.

Our data may be accessed in a way we don’t want. It is already a struggle to know much about off-platform content consumption. For example: how much our community is a source of an AI generated answer. The MCP server may be a significant blind spot as it scales. This means a loss of insights about how our site is used, perhaps an undesirable content extraction / harvesting that may benefit our competition… Overexposing the content may change the nature of the community, optimizing it for content retrieval at the expense of being a living expert network.

I’d like to reinforce the initial idea here to make sure that community managers are able to control at a granular level who has access to the MCP server.

Along with it, we have currently no visibility in the usage of the MCP server: who connects, for what, when, etc. We need a way to monitor the MCP usage via some dashboards or something in the data lake that we can use to build dashboards.

+1 on both RBAC at MCP level (not object) as well as the ability to report on usage

We’ve already seen this type of functionality with the Gainsight Slack apps, I’d hope that adding similar workflows as part of a user’s permissions and profile isn’t a major lift.

Saying it falls to the LLM to implement this type of gating is not a viable solution.