Repository navigation
Enterprise "Registry only" MCP policy blocks local MCP servers in sub-agent processes #35
Description
When using the Microsoft Upgrade Agent plugin with GitHub Copilot CLI, the local built-in MCP servers are accessible in the main CLI session (via manual mcp.json configuration) but are not invokable from sub-agent processes when the enterprise policy is set to "Registry only". Admin has allowed this MCP, but it still don't work via the upgrade agent.
Reacted by jovton
Activity
jovton commentedon Sep 3, 2026
I am noting that the MCP server names/id's and commands/arguments defined by the skill/agent files (
*.md) and used by the sub-agents in%userprofile%\.copilot\installed-plugins\upgrade-agent-plugins\upgrade-agent\agents, are not exactly the same as the one declared in%userprofile%\.copilot\installed-plugins\upgrade-agent-plugins\upgrade-agent\extenders\upgrade-dotnet\upgrade-extension.jsonor in%userprofile%\.copilot\installed-plugins\upgrade-agent-plugins\upgrade-agent\extenders\upgrade-typescript\upgrade-extension.json.Enterprise policies likely block MCP servers that do not match name and/or commands/arguments exactly.
The only proper solution to this is to ask your enterprise security admins to add each MCP server name/id and commands+arguments defined in these
*.mdand*.jsonfiles to their "allow-list" registry of MCP servers in their enterprise security policies.