MCP server 'blocked by policy'
- 主要语言
- Shell
- 星标
- 11.2k
- 派生
- 1.9k
- 平均合并
- 14 小时 16 分钟
- 30 天内合并 PR
- 6
描述
### Describe the bug
We have a custom MCP registry which is checked when local MCP servers are configured. Although the local MCP configuration is correct and works just fine within VSCode and IntelliJ plugin, an error message 'MCP server is blocked by policy' is shown.
It is unclear what causes this. The process log mentions the following:
```
2026-06-25T11:40:36.761Z [ERROR] MCP server "io.github.sooperset/mcp-atlassian" filtered: Server "io.github.sooperset/mcp-atlassian" found in registry but local configuration does not match the registered server identity
```
### Affected version
GitHub Copilot CLI 1.0.65
### Steps to reproduce the behavior
1. Configure an MCP server in the mcp-config.json in the ~/.copilot directory or just install it from within the Copilot CLI with `/mcp add`
2. The MCP server is blocked
### Expected behavior
_No response_
### Additional context
_No response_
贡献指南
调研方向
使用 ~/.copilot 中的 mcp-config.json 或 /mcp add 入口复现该阻止,然后检查进程日志以查找注册表身份不匹配。正确配置的本地 MCP 服务器被接受,而不是被报告为受到策略阻止,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 领域
- cli, security
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 冷清
- 描述清晰度
- 需要澄清
- 新手友好度
- 38/100