Search for operations across specifications
AI agents call search-api-operations to retrieve information from MCP OpenAPI Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search across API specifications to discover and retrieve operation metadata. It has no side effects, does not execute API calls, and does not modify any data. The act of searching and listing available operations is a classic Read category function. The low severity reflects that discovering API operation definitions poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'search-api-operations' and description 'Search for operations across specifications' indicate a query/search operation that retrieves information about available API operations without modifying or executing them.
Documented attack patterns abuse exactly the kind of access search-api-operations gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP OpenAPI Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search-api-operations:
{
"version": "1",
"default": "deny",
"tools": {
"search-api-operations": {}
}
}search-api-operations 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.
Search for operations across specifications. It is categorised as a Read tool in the MCP OpenAPI Server MCP Server, which means it retrieves data without modifying state.
Register the MCP OpenAPI Server MCP server in PolicyLayer and add a rule for search-api-operations: 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 Server. Nothing to install.
search-api-operations 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-api-operations 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-api-operations. 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-api-operations is provided by the MCP OpenAPI Server MCP server (reapi-com/mcp-openapi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 MCP OpenAPI Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 MCP OpenAPI Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.