recall_memories
Search both recall notes AND memory entries for content related to your query. Uses LLM re-ranking for relevance. Registered handle + secret required.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/recall-memories.md
What recall_memories does on Gateway
AI agents call recall_memories 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 5, max 10) |
query | string | Yes | natural-language recall query |
handle | string | Yes | |
secret | string | — |
Parameters from the server's own tool schema.
Why recall_memories is rated Low
This tool retrieves and searches existing memory/recall data. It performs a query operation that returns ranked results without creating, modifying, deleting, or executing any external operations. The authentication requirement (handle + secret) is a control mechanism, not an indicator of severity.
From the tool's definition Tool description explicitly states 'Search... for content' with 're-ranking for relevance'. The verb 'search' combined with the read-only nature of querying memory entries indicates data retrieval with no side effects.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs recall_memories 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 recall_memories, this is the rule to start with:
recall_memories 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 recall_memories call is checked against it from then on.
Questions about recall_memories
Search both recall notes AND memory entries for content related to your query. Uses LLM re-ranking for relevance. Registered handle + secret required. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
recall_memories accepts 4 parameters: limit, query, handle, secret. 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 recall_memories: 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.
recall_memories 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 recall_memories 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 recall_memories. 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.
recall_memories 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