The Pneumetron
NEWSTOOLSINFRASTRUCTURE
Pneumetron.AWS Agent Registry Introduces Custom Metadata Schemas
Share
Skip to article content
  1. Home
  2. ›
  3. News
  4. ›
  5. AI Research
  6. ›
  7. AWS Agent Registry Introduces Custom Metadata Schemas
AI Research·November 18, 2026

AWS Agent Registry Introduces Custom Metadata Schemas

BY PNEUMETRON|4 MIN READ · 877 WORDS4 MIN READ|
Tools
Share

In This Article

  • Enforcing Consistent Governance with Custom Schemas
  • Validation, Compliance, and Approval Workflows
  • Structured Discovery and Filtering
  • Schema Design Constraints and Evolution
  • Implementation Details and Availability
  • Sources
Illustrative photo: switch, it, server, server cabinet
Illustrative image: blickpixel / Pixabay

AWS Agent Registry now supports custom metadata schemas, enabling organizations to enforce standardized key-value attributes across agents, MCP servers, and skills. The feature introduces schema validation, structured approval workflows via EventBridge and Lambda, and precise metadata filtering for discovery.

Key Takeaways

  • 01AWS Agent Registry now supports custom metadata schemas for agents, MCP servers, and skills.
  • 02Schemas enforce consistent key-value pairs with validation and compliance status tracking.
  • 03Approval workflows can be automated using EventBridge rules and Lambda functions.
  • 04Discovery APIs allow filtering records by custom metadata attributes and compliance status.

AWS has added custom metadata schemas to AWS Agent Registry, enabling organizations to define and enforce standardized key-value attributes across all records, including agents, Model Context Protocol (MCP) servers, and skills. The feature, announced on November 17, 2026, addresses the need for a unified vocabulary to govern, discover, and filter agentic resources within a registry.

Custom metadata schemas allow administrators to create a shared set of facts that every record in the registry must carry. This capability ensures that teams use consistent field names and values, which is critical for scaling governance, compliance, and discovery across an agentic fleet.

Enforcing Consistent Governance with Custom Schemas

Administrators define custom metadata schemas by specifying field names, data types, allowed values, and whether each field is required or optional. The registry supports four data types: Text, Enum, URL, and Boolean. Schemas can define attributes that apply to every record type, as well as dedicated fields specific to certain record types, such as networkEgress for MCP servers.

The schema acts as a centralized definition for an organization's resources. For example, a schema might standardize fields such as environment (with allowed values like prod, staging, dev), businessUnit, ownerTeam, supportContact, costCenter, and cmdbId. Security and compliance fields can include dataClassification, complianceScope (such as PCI or HIPAA), riskTier, scanStatus, and scanReportUrl.

By enforcing a common definition, the registry ensures that a field such as environment has the same name and allowed values regardless of which team publishes the record. This consistency allows consumers, agents, and governance tools to rely on a predictable structure when searching or evaluating resources.

Illustrative photo: dictionary, online, technology, internet Illustrative image: tookapic / Pixabay

Validation, Compliance, and Approval Workflows

When a record is created or updated, AWS Agent Registry validates the custom metadata against the active schema. The validation logic enforces strict compliance:

  • Records created without any custom metadata are saved with a NON_COMPLIANT status. This allows teams to save work in progress, but the record cannot be submitted for approval until it includes all required fields and values.
  • If a record includes custom metadata with an unknown field, a missing required field, or an invalid value, the registry rejects it with a ValidationException.
  • The GetRegistryRecord API returns the record's custom metadata values and its compliance status. A COMPLIANT status indicates that the values match the administrator's schema; it does not signify approval. Approval remains a separate decision made by approvers or automation.

The registry supports automated approval workflows triggered by record submissions. When a record moves to Pending approval, AWS Agent Registry emits an event to Amazon EventBridge. An EventBridge rule can invoke a custom AWS Lambda function to evaluate the record. The function reads the record's custom metadata and compliance status to perform checks. For example, an approval function might verify that the record is COMPLIANT, the scanStatus is PASSED, a cmdbId is present, and the dataClassification is within an allowed range. Records failing these checks are rejected with the reason for failure. Functions can also route records requiring human review, such as those with restricted data classifications.

Structured Discovery and Filtering

Custom metadata values are indexed to support precise discovery. The discovery APIs allow consumers to filter records based on custom attributes. A query can combine natural language with specific metadata filters, such as environment=prod AND businessUnit=payments AND securityScanStatus=PASSED. The registry returns only approved records that match the filters, excluding non-compliant or unapproved drafts.

Agents can access the registry via the MCP endpoint at https://agentregistry.<region>.api.aws/registry/<registryId>/mcp, which exposes search, list, and get tools. Agents can translate natural language requests into filtered searches using the defined metadata fields. For instance, an agent can query for "a production MCP server for payments ledger lookups that passed its security scan" and receive results based on the structured metadata.

Illustrative photo: play stone, network, networked, interactive Illustrative image: geralt / Pixabay

Schema Design Constraints and Evolution

Schema changes are strictly additive. Administrators can add new fields, add allowed values to existing enums, or change optional fields to required. However, schemas cannot be modified to rename fields, remove fields, or retype fields.

When a schema is updated, existing records are not rewritten. Records that no longer match the updated schema are reported as NON_COMPLIANT but retain their approval status. If a curator updates an approved record, the revision must meet the new schema requirements; otherwise, the submit fails until all required fields are populated. Until a curator approves the new revision, consumers continue to see the approved version.

The announcement advises treating the schema as a shared vocabulary. Organizations should settle field names and allowed values with the teams that publish and approve records before creating the schema. For fields populated by automation after registration, such as security scan results, the schema should allow interim values like PENDING. Sensitive details, including secrets and internal endpoints, should be excluded from broadly readable metadata.

Implementation Details and Availability

The feature is available in supported AWS Regions. Implementation requires an AWS account, AWS credentials, and IAM permissions for AWS Agent Registry. The sample implementation uses Python 3.11 or later and boto3 1.43.113 or later. The code utilizes the agent-registry-control and agent-registry boto3 clients. A sample repository demonstrating the workflow is available on GitHub.

"Treat the schema as your organization's shared vocabulary," the announcement advises, emphasizing the need to align field definitions with publishing and approving teams to ensure long-term usability.

Sources

  • aws.amazon.com: Govern and discover records with common metadata in AWS Agent Registry | Amazon Web Services
#aws#agentregistry#metadata#governance#mcp#automation
PE
PUBLISHED BY

PNEUMETRON EDITORIAL

Pneumetron's pipeline pairs AI-assisted drafting with human editorial review before publishing — our goal is to make staying informed easier, not to replace real reporting.

Source Material:aws.amazon.com ↗
Share this article
Share
Stay Informed

Never miss a signal.

Subscribe to the Pneumetron Intelligence Digest.

← Previous
Four New AI Papers Advance Reasoning, TTS, and Decoding Efficiency
Next →
OpenAI Deploys GPT-6 Astra and Luna as Healthcare Computer-Use Agents

More from AI Research

View All →
AI Research2h ago
Illustrative photo: glass, reflection, lights, door

AWS Details OAuth Patterns for Bedrock AgentCore to Snowflake Cortex AI

Amazon Web Services published a technical guide detailing three OAuth authentication patterns for routing Bedrock AgentCore AI agents to Snowflake Cortex tools via MCP, addressing enterprise identity and token management requirements.

BY PNEUMETRON6 MIN READ
Read more
AI Research3h ago
Illustrative photo: robot, arm, technology, robot arm

Recent releases advance robot motion adaptation, simulation assets, and decentralized coordination

NVIDIA, researchers, and open-source communities released four tools addressing robot learning bottlenecks: motion retargeting, validated simulation assets, decentralized multi-robot coordination, and human-in-the-loop grasp correction.

BY PNEUMETRON6 MIN READ
Read more
AI Research3h ago
Illustrative photo: network, edp, plug, patch cord

Google rolls out free Gemini Tasks powered by Gemini 4 Hydrogen

Google makes its autonomous Tasks feature free for hundreds of millions across six countries, driven by the new Gemini 4 Hydrogen model optimized for speed, agentic workflows, and secure commerce.

BY PNEUMETRON6 MIN READ
Read more
AI Research3h ago
Illustrative photo: tea somilier, tea room, tea

OpenAI Deploys GPT-6 Astra and Luna as Healthcare Computer-Use Agents

OpenAI has deployed GPT-6 Astra and GPT-6 Luna as computer-use agents that navigate healthcare portals via simulated clicks. Luna costs 8.5 cents per task, while Astra scores 94.3% on Stanford’s HealthAdminBench.

BY PNEUMETRON4 MIN READ
Read more

Comments

In This Article

  • Enforcing Consistent Governance with Custom Schemas
  • Validation, Compliance, and Approval Workflows
  • Structured Discovery and Filtering
  • Schema Design Constraints and Evolution
  • Implementation Details and Availability
  • Sources

Most Read

01
AI Research·1d ago
Recent AI Research Reveals Gaps in Coding Agents and Advances Scientific Modeling
02
AI Research·1d ago
Four New AI Papers Advance Reasoning, TTS, and Decoding Efficiency
03
AI Research·2h ago
AWS Details OAuth Patterns for Bedrock AgentCore to Snowflake Cortex AI
04
AI Research·1d ago
NVIDIA Vera Rubin NVL72 debuts in MLPerf Training v6.1 with up to 2x Blackwell Ultra performance
05
AI Research·1d ago
Anthropic Upgrades Fable and Mythos as Frontier AI Expands Open-Source and Robotics
Daily Digest

Get top AI & tech signals delivered to your inbox every morning.

Subscribe →
Follow Signals
X / TWITTERLINKEDININSTAGRAMYOUTUBETELEGRAM

THE PNEUMETRON

The publication of modern technology, AI, and infrastructure.

AI-assisted, human-reviewed.

NEWS CATEGORIES

  • AI RESEARCH
  • TECHNOLOGY
  • WORLD
  • BUSINESS
  • POLITICS
  • SCIENCE
  • HEALTH
  • SPORTS
  • ENTERTAINMENT

AI & RESEARCH

  • AI RESEARCH
  • INFRASTRUCTURE
  • TOOLS
  • DEEP DIVES
  • TECHNICAL DISPATCHES

RESOURCES

  • ABOUT US
  • CONTACT
  • CAREERS
  • ADVERTISE
Pneumetron.
© 2026 Pneumetron. AI-assisted, human-reviewed.
All rights reserved.
ABOUTTOOLSPRIVACYTERMSCONTACT