Skip to main content
skill CX Codex

implementing-api-schema-validation-security — Claude Code skill

implementing-api-schema-validation-security enforces OpenAPI and JSON Schema validation across API gateways and application code. Blocks injection attacks, mass assignment, and response data leaks.

Apache-2.0 280 installs ★ 36,511 updated 2026-08-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-schema-validation-security -a claude-code
Open on GitHub

What implementing-api-schema-validation-security does

This skill writes API validation contracts using OpenAPI 3.0, 3.1, or JSON Schema draft-07. It defines regex patterns, field boundaries, and sets additionalProperties: false. This setup stops attackers from injecting arbitrary payloads or exploiting mass assignment vulnerabilities.

On the application side, the skill configures runtime checks, such as FastAPI routes using Pydantic models with ConfigDict(extra='forbid'). It also targets gateways like Cloudflare API Shield, Kong, or AWS API Gateway to inspect payloads before they reach application handlers.

Your setup requires OpenAPI specifications and an API gateway or CI/CD runner capable of schema enforcement. Without schema validation on outgoing responses, internal database fields can easily slip through to clients.

What it helps with

  • block SQLi, XSS, and XXE attempts using strict schema constraints
  • prevent mass assignment attacks by rejecting undeclared request fields
  • stop backend data leakage by validating API response contracts
  • configure FastAPI models to reject unexpected payload keys

Example prompts for the agent

  • Generate an OpenAPI 3.1 contract for the user registration endpoint with strict field validation
  • Configure Pydantic models in FastAPI to reject unlisted fields with extra='forbid'
  • Create a schema validation rule for AWS API Gateway to stop unauthorized payload parameters

How to install implementing-api-schema-validation-security

1Skills CLI (Vercel)

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-schema-validation-security -a claude-code

2Manually: put the files in place

~/.claude/skills/implementing-api-schema-validation-security/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/implementing-api-schema-validation-security/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about implementing-api-schema-validation-security

How do I install implementing-api-schema-validation-security in Claude Code?

Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-api-schema-validation-security -a claude-code.

What does implementing-api-schema-validation-security do?

It implements strict API schema enforcement using OpenAPI and JSON Schema across development and runtime environments. This blocks injection vectors, prevents mass assignment, and eliminates response payload data leaks.

Which API gateways work with this schema setup?

It targets gateways that support contract-based request checks, specifically Cloudflare API Shield, Kong, and AWS API Gateway.

Source text

SKILL.md · Apache-2.0
---
name: implementing-api-schema-validation-security
description: Implements API schema validation using OpenAPI Specification and JSON
  Schema documents, enforced both at the API gateway (runtime) and during development
  (shift-left), to lock down request/response contracts and reject unknown properties.
  Use when preventing injection attacks (SQLi, XSS, XXE), blocking mass assignment,
  or stopping data leakage through unvalidated API responses.
domain: cybersecurity
subdomain: api-security
tags:
- api-security
- schema-validation
- openapi
- json-schema
- input-validation
- data-leakage-prevention
- mass-assignment
- api-gateway
version: '1.0'
author: mahipal
license: Apache-2.0
nist_csf:
- PR.PS-01
- ID.RA-01
- PR.DS-10
- DE.CM-01
mitre_attack:
- T1190
- T1059.007
- T1552.001
- T1055
- T1059
---

# Implementing API Schema Validation Security

## Overview

API schema validation enforces that all data exchanged through APIs conforms to a predefined structure defined in OpenAPI Specification (OAS) or JSON Schema documents. This prevents injection attacks (SQLi, XSS, XXE), blocks mass assignment by rejecting unknown properties, prevents data leakage by validating response schemas, and ensures type safety across all API interactions. Schema validation operates at both the API gateway level (runtime enforcement) and during development (shift-left security).


## When to Use

- When deploying or configuring implementing api schema validation security capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation

## Prerequisites

- OpenAPI Specification v3.0 or v3.1 for all API endpoints
- API gateway with schema validation support (Cloudflare API Shield, Kong, AWS API Gateway)
- JSON Schema draft-07 or later understanding
- Development environment with OpenAPI validation libraries
- CI/CD pipeline for automated schema compliance testing

## Core Implementation

### OpenAPI Schema with Security Constraints

```yaml
openapi: 3.1.0
info:
  title: Secure E-Commerce API
  version: 2.0.0
servers:
  - url: https://api.example.com/v2
    description: Production (HTTPS enforced)
security:
  - OAuth2:
      - read:products
      - write:orders

paths:
  /products:
    post:
      operationId: createProduct
      security:
        - OAuth2: [write:products]
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProductCreate'
      responses:
        '201':
          description: Product created
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Product'
        '400':
          $ref: '#/components/responses/ValidationError'
        '401':
          $ref: '#/components/responses/Unauthorized'

  /products/{productId}:
    get:
      operationId: getProduct
      parameters:
        - name: productId
          in: path
          required: true
          schema:
            type: string
            format: uuid
            pattern: '^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$'
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Product'

components:
  schemas:
    ProductCreate:
      type: object
      required: [name, price, category]
      properties:
        name:
          type: string
          minLength: 1
          maxLength: 200
          pattern: '^[a-zA-Z0-9\s\-\.]+$'  # No special chars for injection prevention
        description:
          type: string
          maxLength: 2000
          # Sanitize HTML entities
        price:
          type: number
          format: float
          minimum: 0.01
          maximum: 999999.99
          exclusiveMinimum: 0
        category:
          type: string
          enum: [electronics, clothing, food, furniture, other]
        tags:
          type: array
          items:
            type: string
            maxLength: 50
            pattern: '^[a-zA-Z0-9\-]+$'
          maxItems: 10
          uniqueItems: true
      additionalProperties: false  # CRITICAL: Prevents mass assignment

    Product:
      type: object
      required: [id, name, price]
      properties:
        id:
          type: string
          format: uuid
          readOnly: true
        name:
          type: string
        price:
          type: number
        category:
          type: string
        tags:
          type: array
          items:
            type: string
        createdAt:
          type: string
          format: date-time
          readOnly: true
      additionalProperties: false  # Prevents data leakage of internal fields

    ValidationErrorResponse:
      type: object
      required: [code, message]
      properties:
        code:
          type: string
          enum: [VALIDATION_ERROR]
        message:
          type: string
          maxLength: 500
        details:
          type: array
          items:
            type: object
            properties:
              field:
                type: string
              error:
                type: string
            additionalProperties: false
          maxItems: 50
      additionalProperties: false

  responses:
    ValidationError:
      description: Request validation failed
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ValidationErrorResponse'
    Unauthorized:
      description: Authentication required

  securitySchemes:
    OAuth2:
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: https://auth.example.com/authorize
          tokenUrl: https://auth.example.com/token
          scopes:
            read:products: Read product data
            write:products: Create and update products
            write:orders: Create orders
```

### Server-Side Schema Validation (Python/FastAPI)

```python
"""API Schema Validation Middleware for FastAPI

Enforces strict schema validation on all request and response payloads
to prevent injection, mass assignment, and data leakage attacks.
"""

from fastapi import FastAPI, Request, Response, HTTPException
from fastapi.middleware import Middleware
from pydantic import BaseModel, Field, field_validator, ConfigDict
from typing import List, Optional
import re
import json
from starlette.middleware.base import BaseHTTPMiddleware

app = FastAPI()


# Strict Pydantic models with security constraints
class ProductCreate(BaseModel):
    model_config = ConfigDict(extra='forbid')  # Reject unknown fields (mass assignment)

    name: str = Field(min_length=1, max_length=200, pattern=r'^[a-zA-Z0-9\s\-\.]+$')
    description: Optional[str] = Field(default=None, max_length=2000)
    price: float = Field(gt=0, le=999999.99)
    category: str = Field(pattern=r'^(electronics|clothing|food|furniture|other)$')
    tags: Optional[List[str]] = Field(default=None, max_length=10)

    @field_validator('name')
    @classmethod
    def sanitize_name(cls, v):
        # Prevent XSS via HTML entities
        dangerous_patterns = ['<script', 'javascript:', 'onerror=', 'onload=']
        lower_v = v.lower()
        for pattern in dangerous_patterns:
            if pattern in lower_v:
                raise ValueError(f'Invalid characters in name')
        return v

    @field_validator('description')
    @classmethod
    def sanitize_description(cls, v):
        if v is None:
            return v
        # Strip potential SQL injection patterns
        sql_patterns = [
            r"('|--|;|/\*|\*/|xp_|exec\s|union\s+select|drop\s+table)",
        ]
        for pattern in sql_patterns:
            if re.search(pattern, v, re.IGNORECASE):
                raise ValueError('Invalid content in description')
        return v

    @field_validator('tags')
    @classmethod
    def validate_tags(cls, v):
        if v is None:
            return v
        if len(v) > 10:
            raise ValueError('Maximum 10 tags allowed')
        for tag in v:
            if not re.match(r'^[a-zA-Z0-9\-]+$', tag) or len(tag) > 50:
                raise ValueError(f'Invalid tag format: {tag}')
        return v


class ProductResponse(BaseModel):
    """Response model that explicitly defines allowed output fields.
    Prevents leakage of internal fields like internal_notes, cost_price, etc."""
    model_config = ConfigDict(extra='forbid')

    id: str
    name: str
    price: float
    category: str
    tags: List[str] = []
    created_at: str


class ResponseValidationMiddleware(BaseHTTPMiddleware):
    """Middleware to validate response payloads against schema.
    Prevents accidental data leakage by checking response content."""

    SCHEMA_MAP = {
        '/api/v2/products': {
            'POST': {'response_model': ProductResponse},
            'GET': {'response_model': ProductResponse},
        }
    }

    async def dispatch(self, request: Request, call_next):
        response = await call_next(request)

        # Only validate JSON responses
        content_type = response.headers.get('content-type', '')
        if 'application/json' not in content_type:
            return response

        # Check if endpoint has a registered response schema
        path = request.url.path
        method = request.method

        route_config = self.SCHEMA_MAP.get(path, {}).get(method)
        if not route_config:
            return response

        # Read and validate response body
        body = b""
        async for chunk in response.body_iterator:
            body += chunk

        try:
            data = json.loads(body)
            model = route_config['response_model']
            if isinstance(data, list):
                for item in data:
                    model.model_validate(item)
            else:
                model.model_validate(data)
        except Exception as e:
            # Log the validation failure for security monitoring
            print(f"SECURITY: Response schema violation on {method} {path}: {e}")
            # Return a safe error instead of potentially leaked data
            return Response(
                content=json.dumps({"error": "Internal server error"}),
                status_code=500,
                media_type="application/json"
            )

        return Response(
            content=body,
            status_code=response.status_code,
            headers=dict(response.headers),
            media_type=response.media_type
        )


app.add_middleware(ResponseValidationMiddleware)


@app.post("/api/v2/products", response_model=ProductResponse, status_code=201)
async def create_product(product: ProductCreate):
    # ProductCreate model with extra='forbid' automatically rejects
    # any unknown fields, preventing mass assignment attacks
    # (e.g., attacker trying to set is_admin=true or price=0)
    pass
```

### Cloudflare API Shield Schema Validation

```bash
# Upload OpenAPI schema to Cloudflare API Shield
curl -X POST "https://api.cloudflare.com/client/v4/zones/{zone_id}/api_gateway/user_schemas" \
  -H "Authorization: Bearer ${CF_API_TOKEN}" \
  -H "Content-Type: multipart/form-data" \
  -F "[email protected]" \
  -F "kind=openapi_v3"

# Enable schema validation with blocking mode
curl -X PATCH "https://api.cloudflare.com/client/v4/zones/{zone_id}/api_gateway/settings/schema_validation" \
  -H "Authorization: Bearer ${CF_API_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "validation_default_mitigation_action": "block",
    "validation_override_mitigation_action": null
  }'
```

### CI/CD Schema Compliance Testing

```yaml
# GitHub Actions workflow for schema validation in CI
name: API Schema Security Check
on:
  pull_request:
    paths: ['api/**', 'openapi/**']

jobs:
  schema-security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Validate OpenAPI Schema
        run: |
          npm install -g @stoplight/spectral-cli
          spectral lint openapi.yaml --ruleset .spectral-security.yaml

      - name: Check for Security Anti-Patterns
        run: |
          python3 scripts/schema_security_check.py openapi.yaml

      - name: Run Contract Tests
        run: |
          npm install -g dredd
          dredd openapi.yaml http://localhost:3000 --hookfiles=./test/hooks.js
```

## Security Anti-Patterns to Detect

| Anti-Pattern | Risk | Fix |
|---|---|---|
| `additionalProperties: true` or missing | Mass assignment | Set `additionalProperties: false` |
| No `maxLength` on strings | Buffer overflow, DoS | Add appropriate `maxLength` constraints |
| No `pattern` on string fields | Injection attacks | Add regex patterns to restrict input |
| No `enum` for fixed-value fields | Unexpected input processing | Use `enum` for fields with known values |
| `format: password` without TLS | Credential exposure | Enforce HTTPS-only server URLs |
| Missing error response schemas | Information leakage | Define all 4xx/5xx response schemas |
| `readOnly` fields in request body | Data manipulation | Enforce `readOnly` server-side |

## References

- OpenAPI Specification v3.1: https://spec.openapis.org/oas/v3.1.0
- Cloudflare API Shield Schema Validation: https://developers.cloudflare.com/api-shield/security/schema-validation/
- Redocly API Security by Design: https://redocly.com/learn/security
- Impart Security API Validation: https://www.impart.ai/blog/detect-and-fix-api-vulnerabilities-using-validation-secure-principles-and-real-time-response
- OWASP API Security Top 10 2023: https://owasp.org/API-Security/editions/2023/en/0x00-header/

© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills

Similar skills

All skills for Security →

From the same set152

The whole set →
analyzing-supply-chain-malware-artifacts The analyzing-supply-chain-malware-artifacts skill investigates supply-chain malware artifacts, from altered software updates to tainted builds and sideloaded dependencies. CX Codex +1 293installs scanning-network-with-nmap-advanced scanning-network-with-nmap-advanced — a skill for advanced network reconnaissance with Nmap: host discovery, service version detection, firewall evasion, NSE vulnerability checks, and structured output parsing into XML or CSV. CX Codex +1 286installs achieving-cmmc-level-2-compliance achieving-cmmc-level-2-compliance guides defense contractors through CMMC Level 2 compliance, CUI scoping, NIST SP 800-171 Rev 2 requirements, and SPRS scoring. CX Codex +1 284installs auditing-cloud-with-cis-benchmarks auditing-cloud-with-cis-benchmarks audits AWS, Azure, and GCP environments against CIS Benchmarks using Prowler and ScoutSuite. Useful for baseline checks, finding misconfigurations, and audit prep. CX Codex +1 282installs detecting-ai-model-prompt-injection-attacks The detecting-ai-model-prompt-injection-attacks skill identifies prompt injection attempts against AI models using pattern matching, structural heuristics, and DeBERTa classification. CX Codex +1 280installs analyzing-tls-certificate-transparency-logs analyzing-tls-certificate-transparency-logs queries Certificate Transparency logs via crt.sh to uncover phishing domains and shadow IT. Uses Levenshtein distance to detect brand typosquatting. CX Codex +1 280installs auditing-terraform-infrastructure-for-security auditing-terraform-infrastructure-for-security guides AI assistants through auditing Terraform code with Checkov, tfsec, Terrascan, and OPA. Catches public access, lax IAM rules, and missing encryption before apply. CX Codex +1 279installs analyzing-typosquatting-domains-with-dnstwist analyzing-typosquatting-domains-with-dnstwist builds lookalike domain permutations for a name you own, resolves them, and scores the registered ones by page similarity and registration freshness. CX Codex +1 278installs

Project sponsors

Companies that keep this analytics open