MCP Server Security

Microsoft MCP security: Defender for Endpoint

Microsoft's Defender for Endpoint inventories local AI agents and the MCP servers each has configured on Windows and macOS, using existing device onboarding with Intune or PowerShell. Its support matrix names Claude Code, Claude Desktop, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Windsurf and Kiro, and a third-party report confirmed the breadth of local agent discovery. Runtime protection that inspects the agent loop and blocks risky activity is a public preview, and rules for MCP tools onboarded to Agent 365 can audit or block calls. Agent 365 is listed at $15.00 per user per month. Gaps on 16 Nov 2026: scanning of server code or tool descriptions, an enforced approved-server registry and SIEM export outside Microsoft are none found.

Facts read on .

Strength and weakness for MCP Server Security

Strength: Defender for Endpoint inventories many named local agents and their local and remote MCP servers on Windows and macOS with no extra deployment (microsoft-14, microsoft-15, microsoft-12).

Weakness: None found on 2026-11-16 for scanning MCP servers before use or an enforced approved list; local runtime protection is preview and covers few agents (microsoft-27, microsoft-26).

Scores and evidence

Microsoft is 8th in the overall ranking at 54.5 of 100. Each score below lists the fact ids behind it; the facts follow further down with their sources and read dates.

Microsoft: score per criterion
CriterionScoreWeightWhyFacts
Discovery8 of 1025The vendor names many local clients (Claude Code, Claude Desktop, Cursor, Copilot, Windsurf and others) and lists MCP servers per agent with declared tools; a third-party report confirms broad local agent discovery. Discovery is documented for Windows and macOS only.microsoft-14, microsoft-15, microsoft-16, microsoft-17, microsoft-65
Vetting before use2 of 1020The vendor mentions controlling which tools agents connect to and approving agents before publishing; scanning of server code or tool descriptions and an enforced approved-server registry: none found.microsoft-68, microsoft-69, microsoft-27
Runtime control of tool calls4 of 1020On-endpoint blocking of tool calls is in public preview on Windows with documented limits, so it counts only as a mention; the non-preview control is rules that can block tool calls for MCP tools onboarded to Agent 365, not shown on the machine. Generally available on-machine enforcement with arguments inspected: none found.microsoft-28, microsoft-19, microsoft-23, microsoft-26
Deployment6 of 1015Deployment rides on existing device onboarding with Intune or PowerShell and an OS list is published; a time to deploy: none found.microsoft-12, microsoft-13, microsoft-25
Governance and audit5 of 105Inventory and advanced hunting cover MCP servers and tools, and rules can audit or block tool calls; per-team policy and export to an outside SIEM: none found.microsoft-16, microsoft-17, microsoft-28, microsoft-68, microsoft-39
Transparency8 of 1010Documentation is public and an open-source MCP gateway is observed on GitHub; a price is published for one component but none found for the main product.microsoft-52, microsoft-49, microsoft-51, microsoft-53
Proof6 of 105Third-party press covered the launch of a large established vendor; named customers and analyst coverage for this product: none found.microsoft-64, microsoft-58

Where it ranks

Product, deployment, price and owner

Facts and sources