Get detailed information about a specific API endpoint
AI agents call get_endpoint_details 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.
This tool retrieves and queries endpoint metadata from the OpenAPI specs directory. It performs a read operation—fetching details about API endpoints without modifying, executing, or deleting any data. The description explicitly states 'Get' (retrieval) with no mention of modification, execution, or destructive operations. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'get_endpoint_details' and description 'Get detailed information about a specific API endpoint' indicate retrieval of information with no side effects.
Documented attack patterns abuse exactly the kind of access get_endpoint_details gives an agent:
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_endpoint_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_endpoint_details": {}
}
}get_endpoint_details 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 detailed information about a specific API endpoint. It is categorised as a Read tool in the OpenAPI Directory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenAPI Directory MCP Server MCP server in PolicyLayer and add a rule for get_endpoint_details: 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.
get_endpoint_details 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_endpoint_details 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_endpoint_details. 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_endpoint_details 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.
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.