openapi_summary
Summarise an OpenAPI 3.x or Swagger 2.0 API from a URL (SSRF-safe) or an inline JSON / YAML spec, so an agent can learn an API fast: title, version, servers / base URLs, auth schemes (API key, bearer, OAuth flows), and every operation with method, path, operationId, summary, tags, parameters (wit...
This record as markdown: /tools/com-it-scorptech-x402/openapi-summary.md
What openapi_summary does on ScorpTech x402 API
AI agents call openapi_summary to retrieve information from ScorpTech x402 API 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 |
|---|---|---|---|
tag | string | — | Only operations with this tag |
url | string | — | URL of the spec (JSON or YAML) |
spec | object | — | Inline spec as a JSON object, or a JSON / YAML string (instead of url) |
limit | integer | — | |
search | string | — | Only operations whose path, operationId or summary contains this text |
Parameters from the server's own tool schema.
Why openapi_summary is rated Low
Even though openapi_summary 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.
Risk signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs openapi_summary safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For openapi_summary, this is the rule to start with:
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 ScorpTech x402 API, apply this rule, and every openapi_summary call is checked against it from then on.
Questions about openapi_summary
Summarise an OpenAPI 3.x or Swagger 2.0 API from a URL (SSRF-safe) or an inline JSON / YAML spec, so an agent can learn an API fast: title, version, servers / base URLs, auth schemes (API key, bearer, OAuth flows), and every operation with method, path, operationId, summary, tags, parameters (with $ref resolved), request body types, response codes and per-operation security. Filter by tag or search text. Price: $0.004 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/openapi-summary. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
openapi_summary accepts 5 parameters: tag, url, spec, limit, search. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for 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 ScorpTech x402 API. Nothing to install.
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 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 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.
openapi_summary is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue