Search journal + interaction history for what was discussed. Filter by with_person, about_topic, or both. Returns memory entries and logged touchpoints in time order.
AI agents call recall_conversation to retrieve information from Personal Brain 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 existing journal and interaction history data based on filters (with_person, about_topic). It performs semantic search and returns results in chronological order without creating, modifying, deleting, or executing any external operations. It is a straightforward Read operation.
From the tool's definition Tool description states it "Search[es] journal + interaction history" and "Returns memory entries and logged touchpoints in time order." The verb 'search' and 'returns' indicate pure retrieval with no modification or side effects.
Attacks that exploit this kind of access
Search journal + interaction history for what was discussed. Filter by with_person, about_topic, or both. Returns memory entries and logged touchpoints in time order. It is categorised as a Read tool in the Personal Brain MCP Server, which means it retrieves data without modifying state.
Register the Personal Brain MCP server in PolicyLayer and add a rule for recall_conversation: 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 Personal Brain. Nothing to install.
recall_conversation 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_conversation 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_conversation. 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_conversation is provided by the Personal Brain MCP server (phantomts/personal-brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →