From the source
- AWS added custom metadata schemas to AWS Agent Registry, letting administrators define organization-wide key-value fields that every registered agent, MCP server and skill must carry.
- Until now, organizations had no way to define these facts in the registry and store them on each record, so attributes such as business units, owners and risk classifications could not be tracked consistently.
- An administrator defines field names, types, allowed values and whether each field is required, and the registry validates every record against that schema.
- Records created without custom metadata are saved as NON_COMPLIANT and cannot be submitted for approval until required fields are filled, while unknown fields, missing required fields or invalid values are rejected with a ValidationException.
- GetRegistryRecord returns a record's metadata values and compliance status, and COMPLIANT means the values match the schema rather than that the record is approved.
- Metadata values are indexed for search, so consumers and agents can combine natural-language queries with filters such as environment=prod AND businessUnit=payments AND securityScanStatus=PASSED, and only approved records are returned.






