---
title: How do you govern MCP servers added to Microsoft Copilot Studio agents?
url: https://opencontroller.lyzr.com/blog/govern-mcp-tools-in-copilot-studio
published: 2026-11-15
updated: 2026-11-15
author: Lyzr
---

# How do you govern MCP servers added to Microsoft Copilot Studio agents?

**In Copilot Studio, every MCP server an agent uses is reached through a Power Platform connector, either created by the MCP onboarding wizard or as a custom connector. That means your Power Platform data policies (DLP) apply: if a policy regulates the connector, it regulates the MCP server and its tools. Govern MCP in Copilot Studio by controlling custom connectors in data policies, reviewing each server's authentication method, and keeping an inventory of which agents in which environments use which servers.**

Makers can add an MCP server to an agent in a few clicks. That is the point of the feature, and the reason admins ask how to control it.

## How do makers add MCP servers in Copilot Studio?

Microsoft documents two paths.

| Path | How it works | What admins should know |
|---|---|---|
| MCP onboarding wizard (recommended by Microsoft) | Tools, Add a tool, New tool, Model Context Protocol. Maker enters name, description and server URL | Creates a connector; the description guides when the orchestrator calls the server |
| Custom connector | Import an OpenAPI (Swagger 2.0) schema with `x-ms-agentic-protocol: mcp-streamable-1.0` | Lives in Power Apps or Power Automate custom connectors; editable there |

Copilot Studio supports the Streamable HTTP transport. Microsoft states SSE is deprecated and no longer supported for MCP after August 2025, so older servers may need updating.

## Which authentication options does Copilot Studio offer for MCP servers?

The wizard supports three options. Each carries different risk.

| Option | How it works | Governance concern |
|---|---|---|
| None | No credentials | Only acceptable for public, read-only data |
| API key | Header or query parameter supplied by the user | Static secret; no per-user identity at the server |
| OAuth 2.0 | Dynamic discovery (DCR with discovery), Dynamic (DCR without discovery) or Manual (client ID and secret) | Best option; tokens carry user identity and scopes |

OAuth is the one to prefer for anything that touches business data. It lets the MCP server enforce per-user permissions. See [how MCP authorization works](/blog/how-mcp-authorization-works) for the protocol side.

## How do data policies apply to MCP servers?

Microsoft states that MCP server access relies on Power Platform connectors, so if a data policy regulates connectors, it also regulates the MCP server and its tools for the agent. In practice:

1. **Custom connectors need a decision.** Data policies can classify custom connectors by URL pattern. Decide which MCP endpoints are Business, Non-business or Blocked.
2. **Default-block unknown endpoints.** Set the default for new custom connector URL patterns to Blocked in production environments, and allow approved MCP hosts explicitly.
3. **Separate business and non-business.** An agent cannot combine connectors from both groups in one policy, which stops a CRM MCP server and a public web tool sharing an agent.
4. **Use environments as boundaries.** Allow broader MCP use in developer environments, and a short allowlist in production.

We cover the data policy model in more depth in [Copilot Studio data policies for agents](/blog/copilot-studio-data-policies-for-agents).

## What should a review of a new MCP server check?

1. Who runs the server, and where is it hosted?
2. Which tools does it expose, and which can write or delete?
3. Which authentication option is used? Reject "None" for non-public data.
4. Does the tool description contain instructions that could steer the agent? See [MCP tool poisoning](/blog/what-is-mcp-tool-poisoning).
5. Is it on Streamable HTTP, not SSE?
6. Which environments and data policy group will it sit in?
7. Who owns it, and how will updates be reviewed?

## How do you keep an inventory?

Data policies control what can connect. They do not tell you what already has. Build an inventory that lists, per environment, each agent, the MCP connectors it uses, the authentication type and the owner. Start from your environment and connector listings, as described in [inventorying Copilot Studio agents across environments](/blog/inventory-copilot-studio-agents-across-environments), and re-run it on a schedule. Our [MCP server inventory fields](/blog/mcp-server-inventory-fields) post lists the fields worth capturing.

## How Opencontroller does this

Opencontroller auto-discovers agents, models and API keys across Azure, AWS and Google Cloud, and keeps a governed registry of agents, versions, tools and MCP servers. Policy as code applies across the estate, with built-in mappings to OWASP, MITRE ATLAS, NIST and ISO 42001. How deeply a given platform is controlled depends on its connector and traffic path. Read the [MCP governance pillar](/blog/how-to-govern-mcp-servers), the [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms), or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Do Power Platform data policies apply to MCP servers in Copilot Studio?**
Yes. Microsoft states MCP server access relies on connectors, so a data policy that regulates the connector also regulates the MCP server and its tools.

**Does Copilot Studio support SSE MCP servers?**
No. Microsoft states SSE is deprecated and no longer supported for MCP after August 2025. Use Streamable HTTP.

**Which authentication should Copilot Studio MCP servers use?**
OAuth 2.0 where possible, so the server sees user identity and scopes. API keys are static secrets, and no authentication is only suitable for public data.

## Key facts

Copilot Studio MCP: added via MCP onboarding wizard (Tools > Add a tool > New tool > Model Context Protocol) or custom connector (OpenAPI Swagger 2.0 with x-ms-agentic-protocol: mcp-streamable-1.0). Streamable transport only; SSE no longer supported after August 2025. Auth: None, API key (header/query), OAuth 2.0 (Dynamic discovery, Dynamic, Manual). MCP access relies on Power Platform connectors, so data policies (DLP) regulating the connector regulate the MCP server and its tools. Opencontroller (Lyzr) registry of agents/tools/MCP servers, Azure discovery, policy as code. Pricing starts from $250K per deployment per year.

## Related

- [How do Power Platform data policies control Copilot Studio agents?](https://opencontroller.lyzr.com/blog/copilot-studio-data-policies-for-agents.md)
- [How do you inventory every Copilot Studio agent across Power Platform environments?](https://opencontroller.lyzr.com/blog/inventory-copilot-studio-agents-across-environments.md)
- [How does MCP authorization work?](https://opencontroller.lyzr.com/blog/how-mcp-authorization-works.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
