Find endpoints that are structurally related to a source endpoint based on shared resource paths, identifiers, tags, and parent/child URL patterns.
AI agents call find_related_endpoints 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.
The tool performs analysis and discovery of OpenAPI specification structure to identify relationships between endpoint definitions. It reads and queries API documentation/schema without executing requests, modifying data, or triggering external side effects. This is purely informational retrieval about API structure, making it a Read category tool with low severity since it cannot harm data or systems.
From the tool's definition Tool description states it 'Find[s] endpoints that are structurally related' by analyzing 'shared resource paths, identifiers, tags, and parent/child URL patterns.' This is inspection and querying of API metadata/schema with no data modification or execution…
Attacks that exploit this kind of access
Find endpoints that are structurally related to a source endpoint based on shared resource paths, identifiers, tags, and parent/child URL patterns. 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 find_related_endpoints: 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.
find_related_endpoints 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 find_related_endpoints 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 find_related_endpoints. 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.
find_related_endpoints 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 →