// MCP TOOL REFERENCE

API CONTRACT VALIDATOR TOOLS

5 tools from the Api Contract Validator MCP Server, categorised by risk level.

View the Api Contract Validator policy → Token cost: 604 tokens →

// ALL 5 API CONTRACT VALIDATOR TOOLS

READ 4 tools

Read check_breaking_changes Compare two OpenAPI spec versions to detect breaking changes: removed paths/operations, new required parame... Read diff_request_response Compare a real HTTP request/response against an OpenAPI spec contract. Returns per-field violations. Read lint_api_schema Lint an API spec for quality and best practice compliance. Rules: operation-id-kebab-case, response-success... Read validate_openapi_spec Validate an OpenAPI 3.x or AsyncAPI spec JSON. Returns structural errors, missing required fields, and warn...

WRITE 1 tools

Write generate_mock_from_spec Generate mock response data from an OpenAPI spec. Uses examples, defaults, formats, and type heuristics.

// FAQ

How many tools does the Api Contract Validator MCP server have? +

The Api Contract Validator MCP server exposes 5 tools across 2 categories: Read, Write.

How do I enforce policies on Api Contract Validator tools? +

Route the Api Contract Validator server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard — they are enforced on every call before it reaches the server.

What risk categories do Api Contract Validator tools fall into? +

Api Contract Validator tools are categorised as Read (4), Write (1). Each category has a recommended default policy.

Let agents act without letting them run wild.

Route your MCP servers through PolicyLayer and every tool call is checked against your policy before it runs — allow, deny, or require approval. Per-identity grants. Full audit log. Live in minutes.

SECURE YOUR MCP →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.