Validation based on API input based on Swagger spec

[#1]

The models in our spec have attributes that pretty much describe the input validation rule.

Example:

Member:
    required:
      - hireDate
      - homeContact
    properties:
      id:
        type: integer
        description: will be ignored when included in a request
      remoteIdentifier:
        type: string
        description: the identifier for the member on the system sending/requesting the information
      hireDate:
        type: string
        format: date
      terminationDate:
        type: string
        format: date
      jobTitle:
        type: string
        maxLength: 50
      payrollFrequency:
        type: string
        enum:
          - MONTHLY
          - SEMI_MONTHLY
          - BI_WEEKLY
          - WEEKLY
      ssn:
        type: string
        pattern: '^\d{3}-?\d{2}-?\d{4}$'

I'd like to raise a fault if a call to the endpoint does not conform to the data type, enums, regex etc.

This will serve two needs

a. the API designer builds validation rules into the spec.

b. API automation tests can be generated to assert the rules defined in the spec.

I see a post from 2015 but that requires input validations to be done in javascript. - https://community.apigee.com/questions/5569/policy-to-do-input-validation-based-on-swagger-spe.html

Is there a 'current' best practice to do this?