Return request/response details for a specific endpoint in the discovered OpenAPI document.
AI agents call get_endpoint_details to retrieve information from MCP OpenAPI Discovery without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs no side effects—it simply inspects and returns metadata about an API endpoint (request schemas, response formats, parameters, etc.). It is purely informational and cannot trigger API calls, modify data, or cause irreversible changes.
From the tool's definition The tool 'get_endpoint_details' returns request/response details for a specific endpoint. It retrieves and queries information from the discovered OpenAPI document without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Return request/response details for a specific endpoint in the discovered OpenAPI document. It is categorised as a Read tool in the MCP OpenAPI Discovery MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenAPI Discovery 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 MCP OpenAPI Discovery. 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 MCP OpenAPI Discovery MCP server (rekl0w/mcp-openapi-discovery). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →