sap_memory_search
Free local tool. Full-text search (FTS5) across tool call history. Find patterns, failures, and successes by natural language query. No x402 charge. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-memory-search.md
What sap_memory_search does on Sap
AI agents call sap_memory_search 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 |
|---|---|---|---|
sort | string | — | Sort order. Default relevance. |
limit | number | — | Max results. Default 20, max 100. |
query | string | Yes | FTS5 search query (e.g. "swap failure slippage"). |
offset | number | — | Pagination offset. |
outcome | string | — | Filter by outcome. |
toolName | string | — | Filter by tool name. |
Parameters from the server's own tool schema.
Why sap_memory_search is rated Low
Searches local history without side effects, modifications, or external operations.
From the tool's definition Full-text search (FTS5) across tool call history. Find patterns, failures, and successes.
Attacks that exploit this kind of access
The rule that runs sap_memory_search 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_memory_search, this is the rule to start with:
sap_memory_search 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_memory_search call is checked against it from then on.
Questions about sap_memory_search
Free local tool. Full-text search (FTS5) across tool call history. Find patterns, failures, and successes by natural language query. No x402 charge. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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_memory_search accepts 6 parameters: sort, limit, query, offset, outcome, toolName. 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_memory_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 Sap. Nothing to install.
sap_memory_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 sap_memory_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 sap_memory_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.
sap_memory_search 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