You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MCP servers blocked by policy on GHE — unable to find "MCP servers in Copilot" policy setting #25626
When running an Agentic Workflow on GitHub Enterprise, Copilot CLI blocks both MCP servers at startup:
! 2 MCP servers were blocked by policy: 'github', 'safeoutputs'
This prevents the agent from using any GitHub MCP tools or safe outputs. The agent executes successfully (32 turns, 683K
tokens) but cannot access repos, issues, or PRs because the MCP tools are unavailable.
Environment
GHE instance: ...
gh-aw version: v0.67.1
Engine: Copilot CLI (latest)
MCP Gateway: v0.2.14
AWF version: v0.25.13
Run IDs: 69122712, 69149652, 69158042 (all reproduce the same issue)
What we've verified
Copilot Business is enabled at the enterprise level for the org
COPILOT_GITHUB_TOKEN is a valid fine-grained PAT with Copilot Requests: Read-only
GH_AW_GITHUB_MCP_SERVER_TOKEN tested with both fine-grained PAT and classic PAT (repo + read:org scopes) — same result
The MCP Gateway starts correctly and loads both servers:
✓ github: connected
✓ safeoutputs: connected
✓ All checks passed (2 succeeded, 0 skipped)
The blockage happens after the gateway is ready, when Copilot CLI itself refuses to connect due to policy
Key observation
The MCP Gateway health checks pass — both servers are reachable and responding. Copilot CLI blocks the connection before even
attempting to authenticate. This is a policy enforcement issue, not a token or network issue.
Org Copilot settings
Under the org's Copilot settings (/organization/l....), only "Access" and "Cloud
agent" sections are visible in the sidebar. There is no "Policies" tab where we could enable "MCP servers in Copilot".
Relevant logs
agent-stdio.log:
! 2 MCP servers were blocked by policy: 'github', 'safeoutputs'
@copilot update copilot driver JavaScript code to detect MCP policy issues and surface this error in the actions failure issue/comment with a delightful actionable message with progressive disclosure.
Activity
lpcox commentedon Apr 10, 2026
@apenab this regression is caused by an update to copilot. try upgrading to gh-aw v0.67.4 which pins copilot to a working version.
pelikhan commentedon Apr 11, 2026
@copilot update copilot driver JavaScript code to detect MCP policy issues and surface this error in the actions failure issue/comment with a delightful actionable message with progressive disclosure.
See this kind of text:
MCP servers were blocked by policy:
pelikhan commentedon Apr 11, 2026
See also #25550
chore: update community contributions (2026-04-13)