MCP and A2A governance starts with blocking custom connectors
Diesen Beitrag auf Deutsch lesen
Copilot Studio MCP and A2A connections create custom connectors, so Power Platform admins should block them by default and allow only approved URL patterns.
TL;DR
Copilot Studio MCP and A2A connections create custom connectors in the Power Platform environment. In data policies, setting custom connectors to Ignore allows them by default. Admins should set the default rule to Blocked, permit only required URL patterns, inspect each connector’s OpenAPI definition, and maintain an emergency way to stop agents.
Original by Karl-Johan Spiik, on Karlex. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Treat every MCP or A2A URL as an external dependency and expect admin approval, because each connection creates a custom connector.
- Admins/CoE: Set custom connector policy defaults to Blocked and allow only required URL patterns, then inspect OpenAPI definitions to identify the real host.
- Security/Compliance: Review returned payloads, permissions, credentials and external data handling, because MCP servers can be black boxes and sensitivity labels do not travel externally.
- Leadership/Business: Require documented stop procedures for every agent, because disabling a connection can take up to 48 hours to take effect.
Frequently asked questions
What does Ignore mean for custom connectors in a Power Platform data policy?
Ignore allows custom connectors by default. Set the default rule to Blocked and add only the URL patterns that are needed.
How can Power Platform admins identify the real server behind a custom MCP connection?
Open the custom connector in the solution and inspect its OpenAPI definition. The actual MCP server host appears there, regardless of the connection name.
How quickly does disabling a dangerous MCP or A2A connection take effect?
Disabling can take up to 48 hours to stop use. In an emergency, stop the agent for at least one hour.