Lists all endpoints from the Swagger definition including their HTTP methods and descriptions. Priority: CLI --swagger-url > swaggerFilePath parameter.
AI agents call listEndpoints to retrieve information from Swagger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about available endpoints from a Swagger specification without creating, modifying, executing, or deleting anything. It is purely informational retrieval with no side effects, making it a Read category risk. Severity is low because listing metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool description states it 'Lists all endpoints from the Swagger definition' — a retrieval operation with no modification, execution, or deletion. The name 'listEndpoints' and verb 'Lists' confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access listEndpoints gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swagger MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for listEndpoints:
{
"version": "1",
"default": "deny",
"tools": {
"listEndpoints": {}
}
}listEndpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists all endpoints from the Swagger definition including their HTTP methods and descriptions. Priority: CLI --swagger-url > swaggerFilePath parameter. It is categorised as a Read tool in the Swagger MCP MCP Server, which means it retrieves data without modifying state.
Register the Swagger 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. 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 server (vizioz/swagger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Swagger MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Swagger MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.