Skip to main content
Microsoft · 2 min read · By Hanah Darley

Geordie extends Microsoft partnership to support the Agent Control Specification

Geordie is supporting and helping to shape Microsoft's Agent Control Specification, and Beam now imports and exports policies in ACS-compatible formats.

Geordie is extending our partnership with Microsoft to support and help shape the Agent Control Specification (ACS), previously known as Agent Shield. With ACS, Microsoft is creating a common way for teams to apply runtime controls to agents as they act, and our contribution draws on the work we do with customers every day: understanding agent behavior, governing tool use and applying controls in production across cloud, code and endpoint.

For customers, the value is flexibility. Agent platforms, frameworks and deployment patterns will keep changing, and shared runtime standards mean teams shouldn’t have to rebuild their governance every time their agent stack does.

What Beam now supports

Beam now imports and exports policies in formats aligned with ACS, directly from the Beam policy editor and without manual translation. Teams can author, test and manage a policy in Geordie, then enforce it through Beam or export it into an ACS-compatible environment where that is the better fit. Beam already supports open policy formats including Cedar, and ACS support extends that into Microsoft’s runtime governance ecosystem, including Rego-based implementations where relevant. Beam remains the primary way Geordie customers define and apply controls, with ACS as another path for the same policy.

An example: controlling MCP access

Suppose a developer has built an agent that can reach an MCP server for querying logs, metrics and infrastructure data, and the organization decides that server is out of scope for that agent. A security or platform team can write a Beam policy restricting which tools the agent can invoke and under what conditions. If Beam enforces it, the attempted tool call is evaluated at runtime and blocked before the MCP server is reached, and the agent receives a structured refusal. If the policy is exported to an ACS-compatible runtime instead, the same intent is enforced through that environment’s own model.

We’ll keep working with Microsoft across our existing integrations, including Copilot Studio and Azure AI Foundry, and on initiatives like ACS, so that the controls customers set in Geordie travel with their agents wherever they run.

See every agent across every platform, in one place

Book a demo