Controlling allow/ask/deny lists for predelivered MCP connectors

[Leembo]

Hello,

We are looking at utilizing the pre-delivered MCP connector to M365 via Genie One. The connector works great, but each user can individually configure the allowable tool calls without any central governance layer.

Are we missing something or is that currently a gap in pre-delivered connectors? Ideally, as an account administrator I would be able to select which tools are completely denied at a tenant level for users as a guardrail. 

I know you can do that for externally registered MCP connectors by managing it at a catalog level, is that going to be possible for predelivered MCP connectors as well?

Thanks,
Linas M. 

[DB-RKL]

Hey @Leembo 

system.ai.microsoft_365 is now a 1st class UC object ("MCP service") that runs through Unity Gateway, same as the external connectors you register yourself.

Two levels of control:

- Whole connector on/off:  an EXECUTE grant, so you can allow/deny M365 per user/group centrally today (GA).
- Denying specific tools tenant-wide w/ service policies: guardrails you attach to the MCP service to allow/deny/require-approval on individual tool calls. Service Policies are what enforce a per-tool denylist centrally so the per-user toggles can only pick within what you've allowed up top. (Beta)

I hope this helps