getEndpointCategories
AI agents call getEndpointCategories to retrieve information from Swagger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name and context suggest this tool retrieves categorical information about endpoints from the OpenAPI specification—a read-only operation with no side effects. The empty description reduces confidence slightly, but the naming pattern aligns with other Read tools on the server (getApiDocumentation, getExample, getSchema). Blast radius is minimal as it only exposes schema metadata.
From the tool's definition Tool name 'getEndpointCategories' indicates a retrieval operation that queries endpoint metadata. Server description emphasizes 'query API endpoints, schemas' without modification. No description provided for this specific tool.
Documented attack patterns abuse exactly the kind of access getEndpointCategories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swagger, and nothing reaches the server without passing your rules. This is the rule we recommend for getEndpointCategories:
{
"version": "1",
"default": "deny",
"tools": {
"getEndpointCategories": {}
}
}getEndpointCategories 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.
getEndpointCategories. It is categorised as a Read tool in the Swagger MCP Server, which means it retrieves data without modifying state.
Register the Swagger MCP server in PolicyLayer and add a rule for getEndpointCategories: 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. Nothing to install.
getEndpointCategories 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 getEndpointCategories 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 getEndpointCategories. 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.
getEndpointCategories is provided by the Swagger MCP server (salacoste/openapi-mcp-swagger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Swagger, 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.
6 Swagger tools catalogued and risk-classified — across an index of 43,000+ MCP servers.