Native MCP enforcement from immutable TrustOps decisions

Verify evaluates canonical evidence once, preserves the organization decision, and compiles the result into Microsoft-managed settings. Verify produces the auditable artifact; your infrastructure deploys it and Microsoft/GitHub enforce it.

DISTRIBUTION STATUS

Marketplace release pending

The enforcement artifact and customer deployment workflow remain available without an extension listing.

Evidence to enforcement artifact

1 · Evidence

Canonical evidence

A stable evidence cutoff and source references make the decision reproducible.

2 · Policy

Organization policy

An immutable version keeps thresholds and resolved server inventory fixed.

3 · Snapshot

ALLOW / DENY / REVIEW / UNKNOWN

Structured reason codes explain every target-neutral decision.

4 · Compile

managed-settings.json

A pure compiler emits deterministic native Microsoft keys plus a separate Verify manifest.

5 · Deploy

Customer GitOps / MDM

Your existing configuration-management system distributes the private artifact.

6 · Enforce

VS Code / GitHub Copilot

Microsoft and GitHub remain the enforcement runtime.

Native policy contract

The generated file uses allowedMcpServers, deniedMcpServers, and, in strict mode, allowManagedMcpServersOnly. It contains no Verify metadata, workstation credentials, wildcards, or local-command rules.

Explore TrustOps • Open API documentation

Responsibility boundary

Verify: evidence, immutable decisions, deterministic artifacts, validation, hashes, and audit history.

Customer: approval and deployment through GitOps, MDM, configuration profiles, or equivalent enterprise tooling.

Microsoft/GitHub: interpretation and enforcement of managed settings inside VS Code and GitHub Copilot.