search_memory_facts
Search YOUR extracted memory facts by topic or entity name. No LLM needed — pure SQL lookup against pre-extracted facts. Scoped to facts from memory you own — registered handle + secret required. Returns entries with topics, entities, action_items, and summary.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/search-memory-facts.md
What search_memory_facts does on Gateway
AI agents call search_memory_facts 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 | topic or entity to search for |
handle | string | Yes | |
secret | string | — | |
namespace | string | — | optional namespace filter |
Parameters from the server's own tool schema.
Why search_memory_facts is rated Low
This is a read-only query operation against a private, scoped memory database. It retrieves data without side effects, modifications, or deletions. The authentication requirement (handle + secret) and scope restriction to user-owned facts further limit risk. Severity is low because blast radius is confined to information disclosure of the user's own memory data.
From the tool's definition Tool performs 'pure SQL lookup' and 'returns entries' with no modification or deletion capability. Description explicitly states 'search' and retrieval of 'pre-extracted facts' scoped to user-owned memory with authentication (registered handle + secret…
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs search_memory_facts 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_facts, this is the rule to start with:
search_memory_facts 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_facts call is checked against it from then on.
Questions about search_memory_facts
Search YOUR extracted memory facts by topic or entity name. No LLM needed — pure SQL lookup against pre-extracted facts. Scoped to facts from memory you own — registered handle + secret required. Returns entries with topics, entities, action_items, and summary. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
search_memory_facts 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_facts: 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_facts 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_facts 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_facts. 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_facts 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