GitHub Copilot Harness Security: Patch, Pin and Govern Your Coding Agents
TL;DR
In one week VS Code fixed ten security advisories, eight of them involving MCP servers, agent tools or the agent host, and froze the Local harness for removal in February 2027. Visual Studio moved Copilot Chat onto the Copilot harness, Copilot CLI tied its built-in MCP server to policy, and Git fixed a clone bug that an agent can trigger just by following Git’s own advice.
Treat the editor fleet like any other agent runtime. Patch to a version floor, pin everyone to the Copilot harness (the one that enforces managed sandbox and permission policy), police MCP, permissions and customisations through Copilot’s managed settings, and prove it with diagnostics, telemetry and a test you expect to fail.
In a hurry? Jump to the version floor, the managed baseline or how to prove it, then come back for the why.




