GitHub Copilot Can Now Force MCP Servers Through Plugins
GitHub shipped two changes on 16 November 2026 that land on the same people: whoever owns the Copilot policy for an enterprise.
The first is a new managed setting. In the changelog's words, administrators "can now require selected GitHub Copilot customizations to come from plugins or managed settings, rather than standalone user or project configuration." MCP servers are one of the five categories it covers.
The second is a retirement. VS Code 1.146 deprecates the Local harness, the older code that runs Copilot agent sessions in the editor, and it will be removed in February 2027. Its replacement, the Copilot harness, is the one the managed sandbox and permission controls actually work in.
Neither is a security incident. Both close a gap I keep hitting in reviews: an agent's tool list is often set by whoever last edited a JSON file in the repository.
What happened
Plugin-only customizations. The setting is called strictPluginOnlyCustomization. GitHub says it "blocks standalone customizations from user and project sources", while customizations delivered by eligible plugins or by managed settings keep working. You can apply it to all five supported categories or pick some:
| Category | What it means here |
|---|---|
| Skills | Skill definitions loaded by Copilot |
| Custom agents | Agent definitions |
| Hooks | Commands run on agent events |
| MCP servers | Local and remote MCP server definitions |
| Executable Copilot extensions | Includes executable canvas providers. Not VS Code Marketplace extensions |
GitHub's own example is to "restrict MCP servers and extensions while leaving skills, agents, and hooks open." The control is for GitHub Enterprise Cloud, for members whose Copilot Business or Copilot Enterprise licence comes from the enterprise or one of its organisations. Setup is in GitHub's guide to managing plugin marketplaces and plugins.
There is an important caveat in the changelog itself: "Plugin-only does not mean enterprise-managed plugins only, and it isn't a marketplace allowlist." On its own, the setting moves MCP servers from a repository file into a plugin. It says nothing about which plugins are acceptable. For that you pair it with strictKnownMarketplaces, described with the rest of the enterprise plugin standards.
The Local harness retirement. The Copilot harness has been the default for new sessions since VS Code 1.143. During what GitHub calls "the three-month transition", the Local harness stays available where policy allows. The temporary enterprise setting that keeps it as the default, vscode.temporaryDefaultToLocalHarness, "will be removed along with the Local harness."
What changes for engineers
MCP server control now has three layers. The existing enterprise managed settings reference already had two MCP keys, and the new setting sits beside them:
| Setting | Question it answers | Notes from the docs |
|---|---|---|
allowedMcpServers |
Which servers may run? | Match on serverName, serverUrl or serverCommand. Across sources, the effective list is the intersection |
deniedMcpServers |
Which servers are always blocked? | Deny wins over allow. First-party Copilot servers, such as the built-in GitHub MCP server, cannot be blocked |
strictPluginOnlyCustomization (new) |
Where may a server definition come from? | Plugins or managed settings only, per category |
strictKnownMarketplaces |
Which plugin sources count? | Setting it "disables the built-in marketplaces. An empty array means complete lockdown" |
The allowlist docs carry a warning worth repeating: users choose server names, so serverName matching proves nothing about what a server is. GitHub tells you to "use serverUrl or serverCommand when you need to enforce the identity of a server." An allowlist entry for github matches any server someone has labelled github.
Support differs by client. The docs' client support table marks strictKnownMarketplaces as supported in Copilot CLI, VS Code, the Copilot app, Copilot in GitHub Actions and JetBrains IDEs, but not in the cloud sandbox. allowedMcpServers and deniedMcpServers are supported everywhere except Copilot in GitHub Actions. If agents run in more than one place, check each row before you assume a policy is enforced.
The new key is not in the reference yet. As of 17 November, the managed settings reference lists strictKnownMarketplaces, enabledPlugins and the MCP keys, but not strictPluginOnlyCustomization. Its JSON shape and per-client support are not documented. I would not write it into a production managed-settings.json from the changelog alone.
The harness choice decides which controls work. The VS Code changelog says the Copilot harness lets administrators "enforce managed runtime permissions and sandbox restrictions that the Local harness cannot enforce", and adds that "selecting the Copilot harness doesn't enable sandboxing." The managed sandbox key, which can force local MCP servers into the sandbox with sandboxMcpServers, applies to "Copilot Agent Host sessions in VS Code." The same goes for assisted permissions, which use an LLM judge to approve tool calls and exist only in Copilot harness sessions. A team still on the Local harness gets none of it.
Customizations do not all carry over. The transition guide says prompt files should be converted to skills, that "hooks have no automatic conversion", and that for MCP servers "input prompts and stored editor secrets don't automatically transfer." Expect broken MCP logins on the first Copilot-harness session, which users will report as "the tools disappeared."
What I ran
Nothing. These are enterprise policy controls and I do not have a GitHub Enterprise Cloud tenant to test them on. Everything above comes from the two changelogs, the managed settings reference and the VS Code guide, read on 17 November 2026.
For reference, this is the shape of the documented keys only. It allows one remote MCP server by URL, one local server by exact command, and plugins from a single internal marketplace:
{
"strictKnownMarketplaces": [
{ "source": "github", "repo": "your-org/copilot-plugins" }
],
"allowedMcpServers": [
{ "serverUrl": "https://mcp.internal.example.com/*" },
{ "serverCommand": ["npx", "-y", "@your-org/mcp-tickets@1.4.2"] }
],
"deniedMcpServers": [
{ "serverUrl": "https://*.ngrok-free.app/*" }
]
}
serverCommand matches the exact command and every argument, and wildcards are not supported. Pinning the package version in the allowlist therefore means a version bump needs a policy change too. That is annoying, and it is also the point.
What to do this week
- Inventory where MCP servers are defined today. Search repositories for
.vscode/mcp.jsonfiles and agent definitions that declare their own servers. Anything that lives there would stop loading once the plugin-only rule covers MCP servers. - Decide the plugin home first. Create the internal plugin repository and set
strictKnownMarketplacesbefore you turn on plugin-only for MCP servers. Without the marketplace rule, any marketplace plugin satisfies it. - Move allowlist entries from
serverNametoserverUrlorserverCommand. Names are user-chosen labels. - Find Local harness users. Check whether
vscode.temporaryDefaultToLocalHarnessis set in your policies. If it is, plan the switch before February 2027, starting with teams that rely on hooks. - Test the sandbox separately. Choosing the Copilot harness does not turn it on. If you want local MCP servers sandboxed, that is the managed
sandboxkey, tested on each client you support.
Why this matters: the plugin and marketplace route is also how malicious code reaches coding agents, as Plugin4Shell showed. Forcing MCP servers through plugins only helps if the set of trusted marketplaces is short. I track MCP client and SDK changes on the MCP changelog tracker.
FAQ
What does strictPluginOnlyCustomization do in GitHub Copilot?
It is an enterprise managed setting that blocks Copilot customizations defined in user or project configuration, so only those delivered by plugins or managed settings load. It can cover skills, custom agents, hooks, MCP servers and executable Copilot extensions, all or a chosen subset.
Does plugin-only mode limit which plugins can be installed?
No. GitHub says it "isn't a marketplace allowlist." To restrict plugin sources, set strictKnownMarketplaces. An empty array blocks all marketplaces, including the built-in ones.
When is the VS Code Local harness removed?
February 2027. VS Code 1.146 deprecated it on 16 November 2026, and the Copilot harness has been the default for new sessions since VS Code 1.143. The enterprise setting that keeps the Local harness as the default will be removed with it.
Can admins block the built-in GitHub MCP server?
No. The managed settings reference says first-party Copilot servers, including the built-in GitHub MCP server, are exempt from deniedMcpServers.
Related: MCP Security in 2026, How to Run MCP Servers in Docker Securely and GitHub Copilot Retires Six Models on 14 December.
Spot an error or something out of date? Email me and I will fix it and log it on the corrections page.
I'm Ajay Kumar — I build and operate PandaStack, an open-source Firecracker microVM cloud for AI agents, and write about the infrastructure and tooling around it.
Need this kind of infrastructure work? See what I do or email hello@ajayk.sh.
Related
Google GTIG: Agents Now Turn Patches Into Exploits Unattended
Google's 17 November 2026 AI Threat Tracker reports exploit_agent, a framework that diffs patches and fires exploits with no human, LiteLLM CVE-2026-40217 used for LLMJacking, and a DPRK cluster planting backdoors in .claude/settings.json.
6 minNov 16, 2026wfx-loot: 4,837 Hijacked GitHub Accounts Pushed a CI Secret Stealer
From 10 November 2026 an attacker used stolen GitHub credentials to probe 61,764 repositories and run a secret stealer in at least 1,806 pipelines. What happened, what I counted on GitHub this morning, and what to check this week.
7 minNov 10, 2026Operation Snowball: Jailbroken DeepSeek Agent Breached a Telecom and 13 Firms
Malbear Labs found an open directory holding 70+ transcripts of an autonomous DeepSeek-based agent that spent two weeks inside a European telecom and 13 hosted organisations, reaching millions of patient records.
6 min