AI agents call memory_recall to retrieve information from Locus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears designed to retrieve or query previously stored project context and conversation history from local memory. This is a read operation with no side effects on data—it accesses information without modification, creation, or deletion.
From the tool's definition Tool name 'memory_recall' indicates retrieval of stored memory/context. Server purpose is 'local persistent memory' storage. Naming convention with other tools (memory_audit, memory_calendar, memory_explore) suggests read-like operations.
Documented attack patterns abuse exactly the kind of access memory_recall gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Locus, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_recall:
{
"version": "1",
"default": "deny",
"tools": {
"memory_recall": {}
}
}memory_recall 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.
memory_recall. It is categorised as a Read tool in the Locus MCP Server, which means it retrieves data without modifying state.
Register the Locus MCP server in PolicyLayer and add a rule for memory_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 Locus. Nothing to install.
memory_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 memory_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 memory_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.
memory_recall is provided by the Locus MCP server (magnifico4625/locus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Locus, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Locus tools catalogued and risk-classified — across an index of 43,000+ MCP servers.