Compare a real HTTP request/response against an OpenAPI spec contract. Returns per-field violations.
Risk signalsAccepts file system path (request.path) · Accepts raw HTML/template content (request.body) · Accepts freeform code/query input (request.params.query) · High parameter count (13 properties)
Part of the Api Contract Validator server.
Free to start. No card required.
AI agents call diff_request_response to retrieve information from Api Contract Validator without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though diff_request_response only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"diff_request_response": {}
}
}See the full Api Contract Validator policy for all 5 tools.
These attack patterns abuse exactly the kind of access diff_request_response gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Compare a real HTTP request/response against an OpenAPI spec contract. Returns per-field violations.. It is categorised as a Read tool in the Api Contract Validator MCP Server, which means it retrieves data without modifying state.
Register the Api Contract Validator MCP server in PolicyLayer and add a rule for diff_request_response: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Api Contract Validator. Nothing to install.
diff_request_response is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the diff_request_response rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for diff_request_response. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
diff_request_response is provided by the Api Contract Validator MCP server (https://api.lazy-mac.com/api-contract-validator/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Api Contract Validator tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.