list_endpoints

List endpoints from a discovered OpenAPI document with optional filtering by tag, method, or path fragment.

Server MCP OpenAPI Discovery rekl0w/mcp-openapi-discovery
Category Read
Risk class Low
Parameters 00 required

What list_endpoints does on MCP OpenAPI Discovery

AI agents call list_endpoints 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.

Why list_endpoints needs a policy

This tool retrieves and enumerates endpoint metadata from an already-discovered OpenAPI specification. It performs no modifications, deletions, or external execution—it simply queries and presents information about available API endpoints. The filtering capabilities are introspective queries, not actions that modify or trigger operations. This is a straightforward Read category tool.

From the tool's definition Tool name 'list_endpoints' combined with description stating it 'List endpoints from a discovered OpenAPI document with optional filtering' indicates data retrieval without side effects.

Questions about list_endpoints

What does the list_endpoints tool do? +

List endpoints from a discovered OpenAPI document with optional filtering by tag, method, or path fragment. It is categorised as a Read tool in the MCP OpenAPI Discovery MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_endpoints? +

Register the MCP OpenAPI Discovery MCP server in PolicyLayer and add a rule for list_endpoints: 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.

What risk level is list_endpoints? +

list_endpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_endpoints? +

Yes. Add a rate_limit block to the list_endpoints 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.

How do I block list_endpoints completely? +

Set action: deny in the PolicyLayer policy for list_endpoints. 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.

What MCP server provides list_endpoints? +

list_endpoints 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.