copilot-mcp-server

The server acts as a proxy to GitHub Copilot CLI, which itself can perform powerful operations like file modification and command execution. The MCP server explicitly exposes and documents security controls such as `allowAllTools`, `allowTool`, `denyTool`, `addDir`, and `allowAllPaths`, which are passed directly to the underlying Copilot CLI. While the server itself uses `cross-spawn` for command execution, it does so to invoke the sandboxed `copilot` CLI. There is no direct `eval` or arbitrary code execution within the MCP server's own logic. The overall security largely depends on how the user configures these tool permissions and directory access controls. Enabling `allowAllTools: true` and `allowAllPaths: true` without careful consideration can introduce significant risks.