Tools · Platform giants
AI agent control planes from platform vendors
These are agent governance features built into platforms a company may already license: a registry of agents, with policy, lifecycle rules and monitoring applied from one console. They differ in how they reach agents built elsewhere: some need those agents registered or routed through the vendor's gateway, and some scan other platforms to find them. A team needs one when agents are being built in several places at once, such as low-code tools, cloud AI services and code, and nobody can list them all or apply one set of rules to them.
Platform giants 3
-
Foundry Control Plane (vendor site, opens in a new tab)
generally availableFor agents built in Microsoft Foundry, and agents from other platforms registered through its AI gateway: traces each run, evaluates production traffic continuously, and applies runtime controls at user input, tool calls, tool responses and outputs to catch PII, indirect prompt injection and prohibited actions. It assigns Entra Agent IDs and shows alerts, cost and compliance across the fleet.
-
Microsoft Agent 365 (vendor site, opens in a new tab)
generally availableControl plane for agents, run from the Microsoft 365 admin center: IT onboards agents with security policy templates, limits which users, data, tools and MCP servers each can use, applies lifecycle rules such as expiring inactive agents and flagging ownerless ones, and logs agent actions. Entra, Defender, Purview and Intune controls extend to agents.
-
MuleSoft Agent Fabric (vendor site, opens in a new tab)
generally availableKeeps a registry of agents, APIs and MCP tools, with scanners that find and register agents and MCP servers running on Amazon, Google, Microsoft, Claude, Databricks, Kong and other platforms. It applies consistent governance to agents wherever they were built and reports AI spend.
The briefing
New AI agent governance tools, by email
The briefing's New Tools section covers the latest governance launches, each linked to the vendor's announcement, next to the news that decides which ones matter. At least once a week, five-minute read, free.
You confirm by email. Unsubscribe in one click.
Questions to ask vendors
Neutral questions for a request for proposal (RFP) or a security questionnaire. No product here is named as the answer.
-
Which agents does the control plane see: only those built on your platform, or also agents built in other clouds, tools and code?
-
Is authorization enforced by an external control point, or does it rely on the agent framework behaving as documented?
-
How fast can we revoke one agent's access without touching any other agent?
-
Are high-risk actions gated behind human approval, and can we define which actions count as high risk?
-
Which of these controls need an extra license or a higher plan?
-
Can agent activity logs be exported to our own security tooling, and in what format?
More questions, grouped by topic: Questions to ask AI agent security vendors.
Related incidents
- AWS patched AgentCorruption, a Bedrock AgentCore flaw that let one prompt reach a whole agent fleet
- A GitHub issue could escalate from a low-privilege Google ADK agent to a privileged one
- SalesBleed flaws in Salesforce Agentforce allowed zero-click data exfiltration and Slack phishing
- Microsoft patched a CVSS 10.0 privilege escalation flaw in Azure AI Foundry
Every record in the AI agent incident database links the sources that reported it.
Missing a product, or found an entry that is out of date? Write to [email protected]. A submission is read, never paid for, and does not guarantee a listing. The glossary defines the terms used here.