Lists all endpoints from the Swagger definition including their HTTP methods and descriptions. Use
AI agents call listEndpoints to retrieve information from Swagger MCP (Multi-API Edition) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries API documentation (endpoints, HTTP methods, descriptions) with no side effects. It does not execute API calls, modify configurations, or access data beyond reading the Swagger/OpenAPI specification structure. This is a pure Read operation with minimal blast radius.
From the tool's definition Tool name 'listEndpoints' and description 'Lists all endpoints from the Swagger definition' indicates retrieval of endpoint metadata without modification or execution of those endpoints.
Attacks that exploit this kind of access
Lists all endpoints from the Swagger definition including their HTTP methods and descriptions. Use. It is categorised as a Read tool in the Swagger MCP (Multi-API Edition) MCP Server, which means it retrieves data without modifying state.
Register the Swagger MCP (Multi-API Edition) MCP server in PolicyLayer and add a rule for listEndpoints: 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 Swagger MCP (Multi-API Edition). Nothing to install.
listEndpoints 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 listEndpoints 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 listEndpoints. 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.
listEndpoints is provided by the Swagger MCP (Multi-API Edition) MCP server (psh4607/swagger-muti-mcp). 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 →