recall
AI agents call recall to retrieve information from Mnemosyne MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the Mnemosyne MCP server's primary function of managing knowledge graphs and the typical semantic meaning of 'recall' as retrieving stored information, this tool most likely queries or retrieves data from the knowledge graph without side effects.
From the tool's definition Tool name 'recall' combined with server context describing 'query' operations on knowledge graphs and 'SPARQL queries' suggests data retrieval.
Attacks that exploit this kind of access
recall. It is categorised as a Read tool in the Mnemosyne MCP MCP Server, which means it retrieves data without modifying state.
Register the Mnemosyne MCP server in PolicyLayer and add a rule for recall: 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 Mnemosyne MCP. Nothing to install.
recall 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 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. 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 is provided by the Mnemosyne MCP server (sophia-labs/mnemosyne-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 →