search_endpoints
AI agents call search_endpoints to retrieve information from OpenAPI Search MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves endpoint information from OpenAPI/Swagger documentation. It has no side effects and performs only read operations against API specification data. The blast radius of misuse is minimal—an AI agent querying endpoints poses no risk to systems or data.
From the tool's definition Tool is part of an 'OpenAPI Search MCP Server' that enables 'query OpenAPI/Swagger documentation' and provides 'tools for comprehensive API exploration.' The tool name 'search_endpoints' combined with the server's stated purpose of querying and exploring API…
Attacks that exploit this kind of access
search_endpoints. It is categorised as a Read tool in the OpenAPI Search MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenAPI Search MCP Server MCP server in PolicyLayer and add a rule for search_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 OpenAPI Search MCP Server. Nothing to install.
search_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 search_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 search_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.
search_endpoints is provided by the OpenAPI Search MCP Server MCP server (sheepion/openapi-search-mcp). 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 →