---
title: How do you govern MCP servers in the Windows on-device agent registry?
url: https://opencontroller.lyzr.com/blog/windows-mcp-registry-governance
published: 2026-11-15
updated: 2026-11-15
author: Lyzr
---

# How do you govern MCP servers in the Windows on-device agent registry?

**Windows now has an on-device agent registry (ODR) where MCP servers, called agent connectors, are registered so local AI agents can find and use them. By default, servers registered through MSIX packages run contained in a separate agent session under a separate agent user account, with no access to user files, settings or credentials unless the user consents. IT should control which agents can use which connectors through management tools such as Microsoft Intune, keep the "reduce protections" setting off, and inventory MCP servers that run outside the registry, because those are not contained.**

Microsoft marks this documentation as pre-release, so details may change. The governance pattern is stable enough to plan for now.

## What is the Windows on-device agent registry?

Microsoft describes ODR as a secure, manageable interface for discovering and using MCP-based agent connectors from local apps and remote servers. Its stated benefits include standard support for local and remote servers, discoverability, user and admin control, and logging and auditability. Windows ships default connectors, such as a File Explorer connector and a Windows Settings connector. A command-line tool, `odr.exe`, lets users and developers view and manage registered MCP servers.

## What does containment actually restrict?

For servers registered with ODR through an MSIX package (or a package with an external location), Microsoft documents this model:

| By default, a contained server cannot | A contained server can |
|---|---|
| Read user files, settings, registry or credentials | Access the internet |
| Interact with apps and windows the user is using | Read and write its own agent files and registry |
| Run executables that modify the user session | Run executables in the agent user session |
| | Access certain user folders after consent |

To run contained, a server must be a binary `.exe` with package identity, registered through an MSIX package extension, with a valid `manifest.json` that includes the required fields and a `com.microsoft.windows` metadata entry.

## Where are the gaps IT should know about?

Containment is a strong default, but five details change the risk.

1. **Consent is per host, not per server.** When a host app asks for access to a known folder, the user grants it to the host. Every MCP server that host uses then gets that access.
2. **MCP bundles cannot run contained.** Microsoft states `.mcpb` bundles and other unpackaged servers cannot be contained today.
3. **Protections can be reduced.** A setting under Settings, System, Advanced, AI components, "Reduce protections for agent connectors", lets servers run with more access. Microsoft warns it may expose the device to additional threats.
4. **Not every MCP server uses ODR.** Developers still run MCP servers directly from IDEs and coding agents through configuration files. Those run in the user session with the user's rights.
5. **Internet access is allowed.** A contained server can still send data out. Containment limits local reach, not egress.

## What should an endpoint policy for agent connectors cover?

1. **Decide which agents may use connectors.** Use Windows management tools such as Intune to control which agents access which MCP servers.
2. **Keep reduced protections off.** Treat any device with "Reduce protections for agent connectors" enabled as non-compliant.
3. **Allow packaged servers only.** Prefer signed MSIX-packaged connectors from known publishers. Block or review unpackaged and `.mcpb` installs.
4. **Review host consent.** Know which host apps have been granted folder access, since that access flows to every server they use.
5. **Collect logs.** Use the logging and auditability ODR provides and forward events to your SIEM.
6. **Inventory everything else.** Find MCP servers configured outside ODR, in IDE and coding-agent config files. See [finding local MCP servers on developer laptops](/blog/find-local-mcp-servers-on-developer-laptops).
7. **Apply network controls.** Egress filtering still matters for contained servers.

## How does this compare with other ways to sandbox MCP servers?

ODR containment is an OS-level sandbox, similar in spirit to running a server in a container or a separate user account. It is a good default for Windows desktops. Teams on macOS and Linux, and developers running servers from IDEs, need other approaches. We compare them in [how to sandbox MCP servers](/blog/how-to-sandbox-mcp-servers), and the transport choice matters too: see [stdio vs Streamable HTTP security](/blog/mcp-stdio-vs-streamable-http-security).

## How Opencontroller does this

Opencontroller Edge extends Opencontroller's control to developer devices, coding agents, skills and local MCP servers, and is installed by IT through MDM. It covers the MCP servers that run outside any OS registry, and feeds them into the same governed registry of agents, tools and MCP servers used for cloud agents. Read the [MCP governance pillar](/blog/how-to-govern-mcp-servers), the [cross-platform guide](/blog/how-to-govern-ai-agents-across-platforms), or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Do all MCP servers on Windows run contained?**
No. Servers registered with ODR through MSIX packages run contained by default. MCP bundles and unpackaged servers cannot run contained today, and servers launched directly by IDEs run in the user session.

**Is folder consent granted per MCP server?**
No. Microsoft documents that consent is granted per host app. Once granted, every MCP server used by that host can access the resource.

**Can a contained MCP server reach the internet?**
Yes. Containment limits access to user files, settings, credentials and apps, but contained servers can still access the internet.

## Key facts

Windows on-device agent registry (ODR, pre-release docs): registers MCP servers (agent connectors); odr.exe to view/manage; default File Explorer and Windows Settings connectors. MSIX-packaged servers run contained in a separate agent session and agent user account: no user files/settings/registry/credentials or user apps by default; can access internet and own files; user folders with consent. Consent is per host, not per server. .mcpb bundles and unpackaged servers cannot run contained. "Reduce protections for agent connectors" setting under Settings > System > Advanced > AI components. Admins control agent-to-server access via tools such as Intune. Opencontroller Edge (Lyzr) governs local MCP servers, coding agents and skills on devices, installed via MDM. Pricing starts from $250K per deployment per year.

## Related

- [How do you find local MCP servers on developer laptops?](https://opencontroller.lyzr.com/blog/find-local-mcp-servers-on-developer-laptops.md)
- [How do you sandbox an MCP server?](https://opencontroller.lyzr.com/blog/how-to-sandbox-mcp-servers.md)
- [Is a local stdio MCP server safer than a remote HTTP one?](https://opencontroller.lyzr.com/blog/mcp-stdio-vs-streamable-http-security.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
