Skip to content
context AI agents

AWS Agent Registry Introduces Custom Metadata Schemas for Agent and MCP Server Governance

clearly official source

AWS Agent Registry now allows defining custom metadata schemas for agents, MCP servers, and skills. The administrator sets required fields (owner, environment, compliance scope); records without them are non-compliant and cannot be approved.

AWS has introduced the custom metadata schemas feature in its AWS Agent Registry service — custom metadata schemas for standardized management of agents, MCP servers, and skills. The registry administrator defines a set of key-value fields (of type Text, Enum, URL, or Boolean) that every record in the registry must satisfy, for example environment (prod/staging/dev), businessUnit, ownerTeam, costCenter, data classification, compliance scope (PCI, HIPAA), or securityScanStatus.

According to AWS, the registry validates this metadata when a record is created or updated: a record without filled-in metadata is saved as NON_COMPLIANT and cannot be submitted for approval; a record with an unknown field, a missing required field, or an invalid value is rejected with a ValidationException error. The COMPLIANT status only means conformity with the administrator's schema, not approval itself — that is carried out separately by approvers.

Validated metadata is indexed for search, so a consumer or agent can combine a text query with filters on attributes (e.g., environment=prod AND businessUnit=payments AND securityScanStatus=PASSED), with only approved records being returned. AWS demonstrates the feature using the example of a fictional organization, AnyCompany, publishing an MCP server for banking ledger lookups, where security scanners and CMDB synchronization write metadata values via the API even before submission for approval.

To try out the feature, AWS states the need for an AWS account, IAM permissions for AWS Agent Registry, Python 3.11+, and boto3 version 1.43.113 or newer; a sample implementation is available in the GitHub repository of AWS. The source article is truncated, and the rest of the procedure (registration, enrichment, and approval steps) is missing from the available text — for details, see the source article.

What changed

Why it matters

Organizations running dozens to hundreds of agents and MCP servers have so far been unable to enforce a consistent description of ownership, environment, or security status for these resources — the feature addresses this by having the registry itself block incomplete or invalid records before they reach approval or search. This makes it possible to connect automated security scanners and CMDB systems directly to the approval process and to filter available agents according to compliance requirements (PCI, HIPAA) without manually checking each record.

Two audiences, two different impacts

What this means

01

For individuals

A developer publishing an agent or MCP server to AWS Agent Registry must now fill in organization-defined required metadata, otherwise the record is saved as non-compliant (NON_COMPLIANT) and cannot be submitted for approval; a missing or invalid field results in a ValidationException error.

What to do When working with AWS Agent Registry, check what metadata schema the administrator requires before submitting an agent or MCP server record for approval.
More practical updates →
02

For a business

Companies running their own fleet of agents and MCP servers gain a tool for enforced governance: the administrator defines required fields (e.g., environment, business unit, security scan status, compliance scope PCI/HIPAA), and the registry itself blocks approval of records that do not satisfy these fields or contain invalid values.

Risks and compliance
What to decide Consider introducing a standardized metadata schema (owner, environment, compliance scope) for your internal registry of AI agents and MCP servers.
More business impacts →
Agent Registry AWS custom metadata Governance MCP

Check the original

Event sources

clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.

1
AWS Machine Learning Blog primary source · first detected Govern and discover records with common metadata in AWS Agent Registry