Hybrid search in CURRENT project only with neural reranking.
AI agents call memory_recall_project to retrieve information from Memory-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
memory_recall_project retrieves and queries stored memories from the current project using search mechanisms. It has no side effects, does not modify or delete data, and does not execute external operations. This is a straightforward read/query operation fitting the 'Read' category. Severity is low because even if misused by an AI agent, it only retrieves existing information without causing harm.
From the tool's definition Tool performs 'search' in project memory with 'hybrid search' and 'neural reranking' - purely retrieval operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Hybrid search in CURRENT project only with neural reranking. It is categorised as a Read tool in the Memory-MCP MCP Server, which means it retrieves data without modifying state.
Register the Memory- MCP server in PolicyLayer and add a rule for memory_recall_project: 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 Memory-MCP. Nothing to install.
memory_recall_project 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_project 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_project. 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_project is provided by the Memory- MCP server (wb200/memory-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 →