Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas
AI agents call get-api-catalog to retrieve information from MCP OpenAPI Server 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 metadata about available APIs, operations, and schemas. It has no side effects, does not modify data, execute code, delete anything, or move money. It is a straightforward read operation that enables discovery of available API documentation within the development environment.
From the tool's definition Tool name is 'get-api-catalog' and description states it 'Get the API catalog' and 'contains metadata about all openapi specifications, their operations and schemas' — purely retrieval with no modification.
Documented attack patterns abuse exactly the kind of access get-api-catalog gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP OpenAPI Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-api-catalog:
{
"version": "1",
"default": "deny",
"tools": {
"get-api-catalog": {}
}
}get-api-catalog 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.
Get the API catalog, the catalog contains metadata about all openapi specifications, their operations and schemas. It is categorised as a Read tool in the MCP OpenAPI Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenAPI Server MCP server in PolicyLayer and add a rule for get-api-catalog: 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 Server. Nothing to install.
get-api-catalog 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 get-api-catalog 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 get-api-catalog. 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.
get-api-catalog is provided by the MCP OpenAPI Server MCP server (reapi-com/mcp-openapi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 MCP OpenAPI Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP OpenAPI Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.