Snyk makes Evo ADS MCP Governance generally available
Snyk announced on 30 Sep 2026 that Govern Agent Behavior in Evo ADS is generally available, starting with MCP Governance. Snyk says teams can define approved MCP servers, see agents reach outside the list, and log or block the call on the endpoint across Claude Code, Cursor, Codex and GitHub Copilot.
Facts read on .
Per Snyk's post, MCP Governance does three things: it lets security and platform teams set which MCP servers are approved, from an existing inventory, a curated list or servers found by discovery; it monitors MCP activity on developer machines and flags any agent reaching for a server off the list; and it can log the use for audit or block it at the moment the agent tries to connect.
Snyk says enforcement runs through lightweight hooks beside the agent rather than a proxy or gateway, with policy kept centrally. It names Claude Code, Cursor, Codex and GitHub Copilot as supported today. Snyk also cites its own scan data from nearly 10,000 developer environments: 4,524 unique MCP servers in use and 1 in 12 developers with an MCP server holding a high or critical finding.
Snyk's post describes the release as a first use case and says policy beyond a static allow list, such as risk-based enforcement, is still coming. These are vendor statements; Snyk gives no price in the post.
Sources
- Evo ADS MCP Governance Goes GA, Snyk (snyk.io), read