Multiple Copilot-engine workflows are failing because the Copilot CLI refuses all MCP server connections due to an enterprise or organization policy gate.
Problem
Affected workflows fail with:
🔒 MCP Servers Blocked by Policy: The Copilot CLI blocked MCP server connections due to an organization or enterprise policy. The agent ran without access to MCP tools (GitHub API, safe outputs, etc.).
This is a policy configuration issue, not a transient error — retrying will not help.
Without MCP access, workflows cannot call the GitHub API or emit safe outputs, causing every run to fail.
Affected Workflows / Runs
| Workflow |
Run |
Engine |
Started |
| Test Quality Sentinel |
§24580129809 |
copilot |
18:17 UTC |
| Auto-Triage Issues |
§24581292756 |
copilot |
18:45 UTC |
Additional copilot-engine workflows that ran without failing in the current window (Design Decision Gate, Issue Monster, PR Triage Agent) appear to succeed — suggesting the policy may be intermittently applied or triggered by specific workflow configurations.
Root Cause
Enterprise or organization-level Copilot policy does not permit MCP server connections. The Copilot CLI enforces this gate before the agent starts, so the agent gets no tools and the workflow fails.
Proposed Remediation
An organization or enterprise administrator must:
- Go to enterprise or organization settings
- Navigate to Policies → Copilot
- Enable "MCP servers in Copilot"
See the official documentation.
Note: On some GHE instances the Policies tab is only visible at the enterprise level, not the org level.
Success Criteria
Test Quality Sentinel and Auto-Triage Issues complete with MCP tool access. The mcp_policy_error output flag is absent from the conclusion step.
References:
Generated by [aw] Failure Investigator (6h) · ● 498.9K · ◷
Multiple Copilot-engine workflows are failing because the Copilot CLI refuses all MCP server connections due to an enterprise or organization policy gate.
Problem
Affected workflows fail with:
Without MCP access, workflows cannot call the GitHub API or emit safe outputs, causing every run to fail.
Affected Workflows / Runs
Additional copilot-engine workflows that ran without failing in the current window (Design Decision Gate, Issue Monster, PR Triage Agent) appear to succeed — suggesting the policy may be intermittently applied or triggered by specific workflow configurations.
Root Cause
Enterprise or organization-level Copilot policy does not permit MCP server connections. The Copilot CLI enforces this gate before the agent starts, so the agent gets no tools and the workflow fails.
Proposed Remediation
An organization or enterprise administrator must:
See the official documentation.
Success Criteria
Test Quality Sentinel and Auto-Triage Issues complete with MCP tool access. The
mcp_policy_erroroutput flag is absent from the conclusion step.References: