search_memory
Full-text search over YOUR memory values using FTS5. Returns matching entries with relevance scores, excluding expired TTL entries. Scoped to memory you own — registered handle + secret required. Omit namespace to search all of your own memory.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/search-memory.md
What search_memory does on Gateway
AI agents call search_memory to retrieve information from Gateway 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 | integer | — | max results (default 20, max 100) |
query | string | Yes | FTS5 search terms (porter stemmer, unicode61 tokenizer) |
handle | string | Yes | |
secret | string | — | |
namespace | string | — | namespace to search within (omit to search all of yours) |
Parameters from the server's own tool schema.
Why search_memory is rated Low
This tool retrieves and queries data from a scoped memory store with no side effects. It does not create, modify, delete, or execute operations. The authentication scope and TTL filtering further reduce blast radius.
From the tool's definition Tool description explicitly states it 'returns matching entries' via 'full-text search' with 'relevance scores' — purely a retrieval operation.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs search_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_memory, this is the rule to start with:
search_memory 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 Gateway, apply this rule, and every search_memory call is checked against it from then on.
Questions about search_memory
Full-text search over YOUR memory values using FTS5. Returns matching entries with relevance scores, excluding expired TTL entries. Scoped to memory you own — registered handle + secret required. Omit namespace to search all of your own memory. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
search_memory accepts 5 parameters: limit, query, handle, secret, namespace. Required: query, handle. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for search_memory: 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 Gateway. Nothing to install.
search_memory 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_memory 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_memory. 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_memory is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue