Low Risk

get_endpoints

Get a paginated list of endpoints for a specific API with minimal information

How to control get_endpoints ↓

What get_endpoints does on OpenAPI Directory MCP Server

AI agents call get_endpoints to retrieve information from OpenAPI Directory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_endpoints needs a policy

This tool retrieves and queries endpoint metadata from the OpenAPI Directory. It performs a straightforward read operation—fetching a paginated list of endpoints for a specified API. There is no modification, deletion, execution, or financial impact. The 'minimal information' descriptor further confirms it is a simple data retrieval operation without side effects.

From the tool's definition Tool name 'get_endpoints' and description 'Get a paginated list of endpoints for a specific API with minimal information' indicate data retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access get_endpoints gives an agent:

How to control get_endpoints

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenAPI Directory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_endpoints:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_endpoints": {}
  }
}

get_endpoints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenAPI Directory MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_endpoints

What does the get_endpoints tool do? +

Get a paginated list of endpoints for a specific API with minimal information. It is categorised as a Read tool in the OpenAPI Directory MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_endpoints? +

Register the OpenAPI Directory MCP Server MCP server in PolicyLayer and add a rule for get_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 OpenAPI Directory MCP Server. Nothing to install.

What risk level is get_endpoints? +

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

Can I rate-limit get_endpoints? +

Yes. Add a rate_limit block to the get_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 get_endpoints completely? +

Set action: deny in the PolicyLayer policy for get_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 get_endpoints? +

get_endpoints is provided by the OpenAPI Directory MCP Server MCP server (rawveg/openapi-directory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenAPI Directory MCP Server tool call.

Start from OpenAPI Directory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

22 OpenAPI Directory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.