Low Risk

list_all_apis

List all APIs in the directory with metadata

How to control list_all_apis ↓

What list_all_apis does on OpenAPI Directory MCP Server

AI agents call list_all_apis 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 list_all_apis needs a policy

The tool performs a pure read operation: it lists and retrieves metadata about APIs in a directory. There are no side effects, no code execution, no data modification, and no irreversible actions. Even if an AI agent misuses this tool, the worst outcome is exposure of directory metadata that is presumably public (given it's an 'APIs.guru directory'), resulting in minimal blast radius.

From the tool's definition Tool name is 'list_all_apis' and description states 'List all APIs in the directory with metadata' — this is a retrieval operation that queries and returns information without modifying, executing, or deleting anything.

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

How to control list_all_apis

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 list_all_apis:

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

list_all_apis 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 list_all_apis

What does the list_all_apis tool do? +

List all APIs in the directory with metadata. 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 list_all_apis? +

Register the OpenAPI Directory MCP Server MCP server in PolicyLayer and add a rule for list_all_apis: 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 list_all_apis? +

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

Can I rate-limit list_all_apis? +

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

Set action: deny in the PolicyLayer policy for list_all_apis. 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_all_apis? +

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