util_openapi_breaking_change
Detect removed OpenAPI paths and methods before an agent deploys a client-breaking change.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-openapi-breaking-change.md
What util_openapi_breaking_change does on Delx Mcp A2a
AI agents call util_openapi_breaking_change to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
new_spec | object | Yes | Candidate OpenAPI JSON document. |
old_spec | object | Yes | Previous OpenAPI JSON document. |
Parameters from the server's own tool schema.
Why util_openapi_breaking_change is rated Low
Even though util_openapi_breaking_change only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs util_openapi_breaking_change safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_openapi_breaking_change, this is the rule to start with:
util_openapi_breaking_change is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every util_openapi_breaking_change call is checked against it from then on.
Questions about util_openapi_breaking_change
Detect removed OpenAPI paths and methods before an agent deploys a client-breaking change. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
util_openapi_breaking_change accepts 2 parameters: new_spec, old_spec. Required: new_spec, old_spec. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_openapi_breaking_change: 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 Delx Mcp A2a. Nothing to install.
util_openapi_breaking_change 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 util_openapi_breaking_change 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 util_openapi_breaking_change. 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.
util_openapi_breaking_change is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue