Free Intensive Nov 21–22Free 2-day hands-on Vibecoding Intensive on Nov 21–22 at 16:00 MSK (Sat–Sun) · Live Cohort 3 starts Nov 23Join Free →Cohort 3 (Nov 23)
ReleaseInsight · On RadarGitHub Changelog→ original

GitHub Copilot Lets Admins Restrict MCP and Skills to Plugins Only

In GitHub Copilot for businesses, an admin can require that skills, custom agents, hooks, MCP servers, and extensions load only through plugins or managed settings. The strictPluginOnlyCustomization parameter blocks individual user and project configs, while approved MCP tools are distributed from a shared plugin library. This way, security teams don't have to turn off MCP entirely; they just decide what is allowed.

AI-processed from GitHub Changelog; edited by Hamidun News
GitHub Copilot Lets Admins Restrict MCP and Skills to Plugins Only
Source: GitHub Changelog. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceGitHub Changelog ↗
Editor-in-Chief
Key metric #1The restriction can be enabled for all five categories or for selected ones
Key metric #2You can lock down MCP and extensions while leaving skills, agents, and hooks open
Key metric #3It works in GitHub Enterprise Cloud with Copilot Business and Enterprise licenses

The more capable an AI coding assistant becomes, the sharper the question: who decides what it can connect to? An MCP server gives Copilot access to external systems, a hook runs commands, and an extension executes code. If every developer adds such things to their personal config or to a project repository, the company ends up with a zoo of tools that nobody has vetted. GitHub has added a mechanism for corporate administrators that closes this gap without switching the capabilities themselves off.

What Changed

An enterprise account administrator can now require that selected Copilot customizations come only from plugins or from managed settings. Individual configurations that sit with a user or in a project are blocked. All of this is controlled by the strictPluginOnlyCustomization parameter.

The restriction covers five categories:

  • skills;
  • custom agents;
  • hooks;
  • MCP servers;
  • executable Copilot extensions.

The rule can be applied to all five at once or selectively. For example, you can lock down MCP servers and extensions while leaving skills, agents, and hooks open. An important caveat from the announcement: "extensions" here means executable canvas providers, not extensions from the VS Code Marketplace.

How It Works in Practice

Imagine a company with 500 developers. Previously, any of them could add an MCP server to Copilot that queries a task tracker or an internal database, and nobody knew where that server came from or what it did. The extreme measure is to ban MCP altogether, but then teams lose useful integrations.

Now the approach is different. Security and platform teams build a shared plugin library: a vetted MCP server for the tracker, an approved set of skills, a couple of hooks for code checks. Developers get these tools through plugins, while self-built connections from personal and project configs stop working. Approved plugins and managed settings remain allowed, subject to the organization's other policies.

Plugins Are Not the Same as an Allowlist

GitHub stresses separately that "plugins only" does not mean "only enterprise-managed plugins," and it is not a marketplace allowlist. The strict mode alone only says where a customization may come from. To restrict which marketplaces plugins may be drawn from, you must additionally configure marketplace policies. Existing managed settings can define marketplace sources and require or block specific plugins.

This gives two layers of protection. The first layer: self-made configs don't work. The second layer: plugins come only from permitted sources. If you enable only the first, formally any plugin from any available marketplace remains valid. That's why the settings should be planned together.

Who Can Use It and What to Do

The controls are configured in GitHub Enterprise Cloud for members holding Copilot Business or Copilot Enterprise licenses issued by the enterprise itself or one of its organizations. For individual users and small teams without a corporate account, this doesn't apply.

The practical takeaways for those responsible for development platforms or security:

  • compile a list of the MCP servers, skills, and hooks teams already use;
  • turn the in-demand and safe ones into plugins in the shared library;
  • start with the riskiest categories: MCP servers and executable extensions, because they reach beyond the editor or run code;
  • configure marketplace policies, otherwise control will remain incomplete.

The announcement does not mean GitHub provides ready-made catalogs of approved plugins or automatic security vetting of them. This is a tool for delineating sources, not a guarantee of plugin quality, and the company will have to organize content review on its own. But the ability to permit what's needed and block the rest removes the main argument for a blanket ban on MCP in the corporate environment.

Story

Key Questions Answered

What Changed?

An enterprise account administrator can now require that selected Copilot customizations come only from plugins or from managed settings. Individual configurations that sit with a user or in a project are blocked. All of this is controlled by the strictPluginOnlyCustomization parameter. The restriction covers five categories: skills; custom agents; hooks; MCP servers; executable Copilot extensions. The rule can be applied to all five at once or selectively.

How It Works in Practice?

Imagine a company with 500 developers. Previously, any of them could add an MCP server to Copilot that queries a task tracker or an internal database, and nobody knew where that server came from or what it did. The extreme measure is to ban MCP altogether, but then teams lose useful integrations. Now the approach is different. Security and platform teams build a shared plugin library: a vetted MCP server for the tracker, an approved set of skills, a couple of hooks for code checks.

What are the key details on Plugins Are Not the Same as an Allowlist?

GitHub stresses separately that "plugins only" does not mean "only enterprise-managed plugins," and it is not a marketplace allowlist. The strict mode alone only says where a customization may come from. To restrict which marketplaces plugins may be drawn from, you must additionally configure marketplace policies. Existing managed settings can define marketplace sources and require or block specific plugins. This gives two layers of protection. The first layer: self-made configs don't work.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Hands-On AI Engineering · Hamidun Academy

Build & Ship Production AI Agents Without Boilerplate Code

Start your free 72-hour trial at Hamidun Academy (academy.hamidun.com) — interactive lessons on Claude Code & Cursor, live Tech Radar, and production agent templates.

Start 72h Free Trial →Vibe-Coding Intensive
What do you think?
Loading comments…