LowScript packFree

Copilot AI Governance

Findings for how AI agents, agent identities, and the Copilot agent catalog are governed in Microsoft 365: sponsor/owner coverage, unused agents and tools, assignment-group ownership, broad Graph write permissions on agent identities, unclear agent and blueprint names, classic Copilot Studio servic…

By chadmcox · Version 0.10.0 · Published 19 Nov 2026

← All tests

MP.AIGOV.1053 MCP servers on agents found by Microsoft Defender should use HTTPS, trusted hosts and approval

Severity: MediumGraph

MCP servers set up in Copilot Studio agents or in developer tools on devices don't appear in the agent catalog, so they escape the catalog checks. They still receive your data and run actions, so they need the same rules: encrypted connections, trusted hosts and approval before tools run on published agents.

Remediation action

  • Move MCP servers to HTTPS endpoints on hosts you've reviewed, and remove the ones you haven't.
  • In Copilot Studio, open the agent's Tools, select the MCP server, and require the user to confirm before tools run, then republish.
  • For local agents, change the agent's own MCP configuration on the device.

Related links

%TestResult%

Install
Install-MtPack chadmcox/maester-ai-governance-pack/pack

Assumes Maester is installed. New to Maester? Get started.

Next: connect and run
Connect
Connect-Maester
Run
Invoke-Maester -Pack AIGOV