Given a docs or API URL, detect the OpenAPI/Swagger document behind it and summarize the API structure.
AI agents call detect_openapi to retrieve information from MCP OpenAPI Discovery without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes API specification metadata from a given URL. It performs discovery and inspection only, returning structural information about an API without executing any requests, modifying data, or triggering external operations.
From the tool's definition Tool description states it 'detect[s] the OpenAPI/Swagger document' and 'summarize[s] the API structure' — purely informational operations with no data modification, execution, or side effects.
Attacks that exploit this kind of access
Given a docs or API URL, detect the OpenAPI/Swagger document behind it and summarize the API structure. It is categorised as a Read tool in the MCP OpenAPI Discovery MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenAPI Discovery MCP server in PolicyLayer and add a rule for detect_openapi: 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 MCP OpenAPI Discovery. Nothing to install.
detect_openapi 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 detect_openapi 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 detect_openapi. 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.
detect_openapi is provided by the MCP OpenAPI Discovery MCP server (rekl0w/mcp-openapi-discovery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →