Search project and user memories using local keyword retrieval. Returns relevant memories from prior sessions.
AI agents call recall_memories to retrieve information from Reporecall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries stored memories based on keywords without modifying, deleting, or executing any operations. It is a pure information retrieval operation, fitting squarely in the Read category. The low severity reflects that misuse would only expose potentially sensitive project context, not cause destructive or financial damage.
From the tool's definition Tool description states it "Search[es] project and user memories using local keyword retrieval. Returns relevant memories from prior sessions." The verbs are 'search' and 'returns'—both read operations with no side effects.
Documented attack patterns abuse exactly the kind of access recall_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reporecall, and nothing reaches the server without passing your rules. This is the rule we recommend for recall_memories:
{
"version": "1",
"default": "deny",
"tools": {
"recall_memories": {}
}
}recall_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search project and user memories using local keyword retrieval. Returns relevant memories from prior sessions. It is categorised as a Read tool in the Reporecall MCP Server, which means it retrieves data without modifying state.
Register the Reporecall 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 Reporecall. 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 Reporecall MCP server (proofofwork-agency/reporecall). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Reporecall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Reporecall tools catalogued and risk-classified — across an index of 42,500+ MCP servers.