MCP Schema Validation

The MCP Schema Validation policy validates MCP requests to ensure they conform to the MCP specification

For configuration details, see MCP Schema Validation Policy.

September 2, 2026

Fixed Issues

MCP Schema Validation policy definition and implementation version 1.3.0 is now supported by Omni Gateway.
The policy no longer rejects valid MCP methods from the MCP 2025-06-18 and 2025-11-25 specifications. These methods are now correctly recognized:
- elicitation/create
- sampling/createMessage
- roots/list
- notifications/message
- notifications/resources/list_changed
- notifications/resources/updated
- notifications/prompts/list_changed
- notifications/tools/list_changed
- notifications/elicitation/complete

August 10, 2026

What’s New

MCP Schema Validation policy definition and implementation version 1.2.0 is now supported by Omni Gateway.
Added the Tool Poisoning Detection parameter, which detects tool-poisoning attacks against MCP tools/list responses by pinning the trusted tool set from the API’s Anypoint Exchange asset and comparing every backend tools/list response against it.

May 20, 2026

What’s New

MCP Schema Validation policy implementation version 1.1.2 is now supported by Omni Gateway.

April 20, 2026

What’s New

MCP Schema Validation policy definition version 1.1.1 is now supported by Omni Gateway.