Search and retrieve saved memories with intelligent semantic ranking. 🎯 BASIC SEARCH: recall_memories(query="authentication") → Returns all memories about authentication, ranked by semantic relevance 🔍 FILTERED SEARCH (Phase 2 Knowledge Graph Intelligence): Use filters when you need PRE...
Accepts freeform code/query input (query); High parameter count (10 properties); Single-target operation
Part of the Pūrmemo MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call recall_memories to retrieve information from Pūrmemo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though recall_memories only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
recall_memories:
rules:
- action: allowSee the full Pūrmemo policy for all 11 tools.
Agents calling read-class tools like recall_memories have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Search and retrieve saved memories with intelligent semantic ranking. 🎯 BASIC SEARCH: recall_memories(query="authentication") → Returns all memories about authentication, ranked by semantic relevance 🔍 FILTERED SEARCH (Phase 2 Knowledge Graph Intelligence): Use filters when you need PRECISION over semantic similarity: ✓ entity="name" - Find memories mentioning specific people/projects/technologies Example: entity="purmemo" → Only memories discussing purmemo ✓ has_observations=true - Find substantial, fact-dense conversations Example: has_observations=true → Only high-quality technical discussions ✓ initiative="project" - Scope to specific initiatives/goals Example: initiative="Q1 OKRs" → Only Q1-related memories ✓ intent="type" - Filter by conversation purpose Options: decision, learning, question, blocker Example: intent="blocker" → Only conversations about blockers 💡 WHEN TO FILTER: - Use entity when user asks about specific person/project by name - Use has_observations for "detailed" or "substantial" requests - Use initiative/stakeholder for project-specific searches - Use intent when user asks for decisions, learnings, or blockers 📝 COMBINED EXAMPLES: recall_memories(query="auth", entity="purmemo", has_observations=true) → Find detailed technical discussions about purmemo authentication recall_memories(query="blockers", intent="blocker", stakeholder="Engineering") → Find engineering team blockers. It is categorised as a Read tool in the Pūrmemo MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for recall_memories. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pūrmemo MCP server.
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 Intercept 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 Intercept 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 Pūrmemo MCP server (purmemo/purmemo-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept