sap_search_tools
Search the SAP MCP tool catalog (420+ tools) by keyword. Returns top-K matching tools with their name, description, and full input schema. Use this to discover tools before calling them via sap_call_tool. Categories: sap_phoenix_ (Phoenix perps), sap_adrena_ (Adrena perps), sap_perp_ (perps risk/...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-search-tools.md
What sap_search_tools does on Sap
AI agents call sap_search_tools to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum results to return (default 10, max 25). |
query | string | Yes | Natural language search query. Example: "get Phoenix market data" or "place limit order" or "bridge ETH to Solana". |
category | string | — | Optional category filter (tool name prefix). Example: "sap_phoenix_", "sap_adrena_", "jupiter_", "spl_token_". |
Parameters from the server's own tool schema.
Why sap_search_tools is rated Low
Tool queries a catalog and returns information only; no state modifications or side effects occur.
From the tool's definition Search the SAP MCP tool catalog by keyword. Returns matching tools.
Attacks that exploit this kind of access
The rule that runs sap_search_tools safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_search_tools, this is the rule to start with:
sap_search_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_search_tools call is checked against it from then on.
Questions about sap_search_tools
Search the SAP MCP tool catalog (420+ tools) by keyword. Returns top-K matching tools with their name, description, and full input schema. Use this to discover tools before calling them via sap_call_tool. Categories: sap_phoenix_ (Phoenix perps), sap_adrena_ (Adrena perps), sap_perp_ (perps risk/signals), sap_steve_launch_ (Steve-native Meteora DBC launches), jupiter_ (swaps), spl_token_ (tokens), staking_ (staking), bridging_ (bridges), meteora_ (liquidity), magicblock_ (ephemeral rollups), sap_backpack_ (Backpack Exchange CeFi: markets, depth, klines, collateral, securities, trading), sap_sunrise_ (Sunrise asset gateway: canonical tokens, swap quotes, cross-chain asset swaps), sap_perpspad_ (external PerpsPad launchpad API). Free read. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_search_tools accepts 3 parameters: limit, query, category. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_search_tools: 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 Sap. Nothing to install.
sap_search_tools 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 sap_search_tools 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 sap_search_tools. 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.
sap_search_tools is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap, and thousands of servers like it.
This server
Across the catalogue