util_openapi_summary
Summarize an OpenAPI document including title, version, paths, tags, and likely auth surface.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-openapi-summary.md
What util_openapi_summary does on Delx MCP Server
AI agents call util_openapi_summary to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
url | string | Yes | Origin or direct OpenAPI URL |
timeout | integer | — | Timeout in seconds (1-15) |
Parameters from the server's own tool schema.
Why util_openapi_summary is rated Low
This tool passively analyzes and extracts information from an OpenAPI document—a static specification file. It returns metadata summaries without modifying the document, executing code, or affecting external systems. The output is informational only, making it a Read operation with low blast radius. Misuse would yield only informational leakage, not operational harm.
From the tool's definition Tool name 'util_openapi_summary' and description 'Summarize an OpenAPI document including title, version, paths, tags, and likely auth surface' indicate retrieval and analysis of metadata from an OpenAPI specification document.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs util_openapi_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_openapi_summary, this is the rule to start with:
util_openapi_summary 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 Server, apply this rule, and every util_openapi_summary call is checked against it from then on.
Questions about util_openapi_summary
Summarize an OpenAPI document including title, version, paths, tags, and likely auth surface. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
util_openapi_summary accepts 2 parameters: url, timeout. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_openapi_summary: 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 Server. Nothing to install.
util_openapi_summary 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_summary 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_summary. 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_summary is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue