GitHub is extending enterprise-managed Copilot settings into JetBrains IDEs.
The August 18 release adds centralized controls for plugin governance, MCP server access, OpenTelemetry, and permission modes in GitHub Copilot for JetBrains. Administrators can apply consistent settings across everyone on an enterprise Copilot plan.
The plugin controls let administrators require specific plugins to be enabled or disabled, add approved marketplaces, and restrict installation to known marketplaces. The MCP controls let administrators allow or deny which MCP servers developers can connect to from Copilot for JetBrains.
GitHub also added managed OpenTelemetry settings for collector endpoint, protocol, service name, resource attributes, and content-capture policy. Managed values take precedence over developer settings. A permission-mode setting can prevent the Copilot agent in JetBrains from using Bypass Approvals or Autopilot.
MCP governance is moving into IDE policy
MCP servers and agent plugins are powerful because they connect a coding assistant to tools, data, and workflows. That is also why they need policy.
Without a central allowlist, every developer machine can become a separate integration decision. One person can connect an agent to a local server, internal system, external SaaS tool, or marketplace plugin before security and platform teams understand the boundary.
GitHub’s JetBrains update makes that boundary part of the managed IDE configuration. That is the right layer for many enterprises because agent risk often starts in the developer environment, not only in a deployed production app.
Telemetry and permissions are part of the same control surface
The OpenTelemetry and permission-mode settings are not cosmetic additions.
Telemetry routing decides where agent activity can be observed. Permission modes decide whether the agent can bypass approvals or run in a more autonomous mode. Plugin and MCP settings decide what tools the agent can reach.
Those controls need to be reviewed together. An enterprise can approve a plugin but still restrict the MCP server it talks to. It can allow telemetry but limit content capture. It can permit agent workflows while disabling bypass behavior for repositories with higher risk.
