Skip to content

Image: res.cloudinary.com · rights & removal

Executive Summary

Governing AI coding agents requires a structured approach to managing the Machine Control Plane (MCP) servers they interact with. The proposed method involves four steps: discovering existing MCP servers, defining acceptable risk levels through detailed profiling, observing potential actions before enforcement, and finally, enforcing policies based on those observations. This process leverages Evo Agentic Development Security (ADS) to provide a risk score for MCP servers, allowing for governance based on risk rather than manual review. The system inventories servers running on developer machines and within code repositories to establish an estate overview. Risk profiles detail specific risks like prompt injection, destructiveness, and untrusted content, which inform the decision-making process regarding an allowlist.

Facts Only

* Snyk found 4,524 unique MCP servers in active use across 10,000 developer environments.
* Most observed servers were added quickly without review.
* Evo ADS provides a risk score for MCP servers to enable governance by risk.
* Data is surfaced from MCP servers on developer machines and code repositories.
* Server details include name, origin (e.g., NPM), transport, and local status.
* Risk scores range from 0 (Low) to 1000 (Critical).
* Risk attributes include prompt injection in tool descriptions, destructive capabilities, and untrusted content.
* The allowlist records approved decisions for each server.
* Enforcement blocks calls to servers not on the allowlist if they are rated High or Critical risk at runtime.

Full Take

The structure of this guide moves from raw inventory gathering to high-fidelity, context-aware policy enforcement. The central tension lies between maintaining developer workflow and imposing necessary security controls; the proposed methodology attempts to resolve this by foregrounding observation (Step 3) before implementing restrictive blocking (Step 4). This addresses a common failure point in security tooling: implementing immediate blockages that disrupt productivity without providing contextual evidence. The system successfully shifts governance from a manual, reactive review process (Slack threads) to an automated, proactive risk-based decision framework using empirical data derived from server behavior and code context. However, the reliance on signatures for scoring introduces a limitation, as noted by the exclusion of servers lacking signatures from the primary score, requiring a separate planning consideration. The pattern suggests that true resilience in agentic development requires systems to synthesize environmental state (code, runtime, execution) into actionable risk metrics that developers can trust without sacrificing operational velocity.
Step 1: Discover what’s already running
Step 2: Define what "acceptable" means
Step 3: Observe before you block
Step 4: Enforce, starting with what's risky
Patterns detected: ARC-0024 Ambiguity, ARC-0043 Motte-and-Bailey

From the original · Snyk Blog

November 9, 2026 9 mins readWhen we announced that MCP Governance is generally available in Evo Agentic Development Security (ADS), the most common follow-up was practical: "Great. Where do I start on Monday?"
Read the full story at snyk.io

Sentinel unavailable

The automated check of the source article's wording did not complete, so no result is shown.

This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.

Say Yes To MCP, Safely A Guide For Governing AI Coding Agents With Evo ADS | Huntaegis