Search for API operations by keyword. Returns matching operationIds with summaries.
AI agents call ops_search to retrieve information from Onboarded MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
ops_search performs a query operation that retrieves and displays information about available API operations without creating, modifying, deleting, or executing any operations. It is a discovery/lookup tool that has minimal blast radius if misused—worst case, an agent learns about API operations it could call, but the tool itself causes no state changes.
From the tool's definition Tool description states it 'Search[es] for API operations by keyword. Returns matching operationIds with summaries.' The verb 'search' and return of read-only metadata (operationIds and summaries) indicate no data modification or side effects.
Attacks that exploit this kind of access
Search for API operations by keyword. Returns matching operationIds with summaries. It is categorised as a Read tool in the Onboarded MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Onboarded MCP Server MCP server in PolicyLayer and add a rule for ops_search: 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 Onboarded MCP Server. Nothing to install.
ops_search 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 ops_search 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 ops_search. 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.
ops_search is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-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 →