GitHub Copilot for JetBrains Adds Enterprise Controls for MCP, Plugins, Telemetry, and Permissions
Administrators can restrict plugin sources and MCP servers, route OpenTelemetry, and prevent Bypass Approvals or Autopilot.
Key takeaways
GitHub announced on August 18, 2026 that Copilot for JetBrains now supports enterprise managed settings for plugin governance, MCP server access, OpenTelemetry, and permission modes. Administrators can restrict plugin marketplaces, define allowed and denied MCP servers, route telemetry to an approved collector, and set permissions.disableBypassPermissionsMode to prevent the agent from using Bypass Approvals or Autopilot. Managed values take precedence over developer settings. JetBrains users should therefore verify which enterprise policy is applied before treating a local option as effective. Teams should test blocked MCP connections, telemetry content capture, and approval prompts with a managed test account before rolling the policy out broadly.
Direct answer
JetBrains is now inside the enterprise Copilot guardrail system. A local control being visible does not mean enterprise policy permits it.
Fact sources
GitHub published the JetBrains update on August 18.
The update covers plugins, MCP allowlists, managed OpenTelemetry, and permission modes.
Administrators can block Bypass Approvals and Autopilot with disableBypassPermissionsMode.
Six steps for a managed JetBrains rollout
- Inventory approved plugins, marketplaces, and MCP servers.
- Test a blocked MCP example.
- Set OTLP endpoint and resource attributes.
- Keep content capture off unless approved.
- Disable bypass modes and verify prompts.
- Sign in with a managed test account and verify effective behavior.
Why it matters
Once coding agents call plugins, MCP servers, and commands, risk extends beyond chat text. Central controls reduce client drift but can also distribute a bad policy widely.
Impact for ordinary AI users
Developers may find plugins, MCP servers, or auto-approval modes disabled by policy. That is usually a governance decision, not a local IDE defect.
Related tools and tutorials
Start with one reversible task, verify version, permissions, cost, logs, and accepted output, then record the result in a team checklist.
AI software and tools · AI account and cost services · AI skill tutorials · AI frontier news
FAQ
Can local settings override enterprise values?
Do not assume so; GitHub says managed values take precedence.
Is an MCP server name enough for security matching?
Prefer the documented URL or command matchers for remote and stdio servers.
Does telemetry always capture prompts?
It depends on captureContent and lockCaptureContent; keep content capture off by default.
Source links
- GitHub Changelog: Enterprise managed settings in Copilot for JetBrains (2026-08-18)
- GitHub Docs: Enterprise managed settings reference
- GitHub Docs: Configuring enterprise-managed settings
- GitHub Docs: MCP server usage in your company
What this means for everyday users
Record enterprise, client version, policy source, plugin markets, MCP URL or command, OTLP endpoint, captureContent, permission mode, test account, and effective time.
Related reading
GitHub adds enterprise controls for Copilot agent commands, files, and network access
GitHub released enterprise-managed permissions for Copilot agent operations on September 9. Administrators can centrally set shell commands, file reads and writes, and access to network domains to blocked, approval required, or allowed without a prompt. User preferences, workspace settings, automatic approval, and earlier approvals cannot make the enterprise policy less restrictive. GitHub says the controls are generally available in the Copilot app, Copilot CLI, and Visual Studio Code sessions that use Agent Host for Copilot Business and Enterprise customers. Security and platform teams should begin with a minimum-permission baseline, test representative repositories, and expand only the operations that have a clear owner, audit trail, and rollback path.
AWS connects AgentCore evaluations to GitHub Actions for pre-merge agent regression gates
AWS published a reference workflow on September 8 for integrating Amazon Bedrock AgentCore Evaluations with GitHub Actions. The pipeline deploys a development agent and an OAuth-protected MCP server, invokes representative prompts, collects OpenTelemetry traces, and scores behavior before allowing a pull request to proceed. AWS describes built-in dimensions such as helpfulness, correctness, goal success, tool selection, tool parameters, and trajectory order, with custom and code-based evaluators available. The post compares three authentication patterns: evaluating stored traces, using a pre-authorized test user, or issuing machine-to-machine credentials for CI. Its implementation uses the third pattern. Teams should validate that CI credentials cannot escape their intended environment, that evaluation samples cover important failures, and that score variance, latency, evaluator cost, and rollback behavior are visible before treating the threshold as a release gate.
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows
GitHub Copilot Customize Tab Is Generally Available for Team Agent Workflows. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: configuring team agent behavior in Copilot and validating results with a small task. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
SageMaker AI Adds Script Mode in SDK v3 for Bring-Your-Own-Model Training
SageMaker AI Adds Script Mode in SDK v3 for Bring-Your-Own-Model Training. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: migrating an existing training script to SageMaker while verifying dependencies, data, and cost. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
AWS AgentCore Adds Cross-Account Knowledge Base Connections
AWS AgentCore Adds Cross-Account Knowledge Base Connections. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: enabling an AI agent to securely retrieve from a knowledge base in another account while verifying least-privilege access. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
GitHub Makes Global Model Policy Generally Available for Copilot
GitHub Makes Global Model Policy Generally Available for Copilot. The official source dated August 2026 describes a concrete product, research, or governance change rather than a universal guarantee. This article separates what is available now from preview or planned access, then translates the change into one ordinary-user task: standardizing Copilot model access rules across a team while preserving evidence of policy changes. Before using it, readers should verify account eligibility, workspace permissions, data boundaries, model or service cost, human review, audit logs, and rollback. A small reversible pilot with explicit acceptance checks is safer than copying a headline result or assuming that a new integration can publish, merge, or make decisions without approval. The source set is linked so teams can recheck availability and scope when the product changes.
Summary
Start with a minimal allowlist and content-free telemetry, then validate blocking and approvals with a test account. Verify behavior, not just file presence.
