AI agents call memory_find to retrieve information from Neo4j Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search or query operation on persistent graph-based memory. No description was provided, which lowers confidence slightly, but the semantic relationship with sibling tools (modify, store) and the '_find' suffix strongly suggest this is a retrieval mechanism. Read operations that query data without side effects present low severity risk.
From the tool's definition Tool name 'memory_find' indicates retrieval/search functionality. Description is empty, but given it's part of a memory system alongside 'memory_modify' and 'memory_store', and its naming convention, 'memory_find' is a read operation that queries/retrieves…
Documented attack patterns abuse exactly the kind of access memory_find gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Neo4j Memory Server, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_find:
{
"version": "1",
"default": "deny",
"tools": {
"memory_find": {}
}
}memory_find 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_find. It is categorised as a Read tool in the Neo4j Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Neo4j Memory Server MCP server in PolicyLayer and add a rule for memory_find: 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 Neo4j Memory Server. Nothing to install.
memory_find 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_find 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_find. 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_find is provided by the Neo4j Memory Server MCP server (sylweriusz/mcp-neo4j-memory-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Neo4j Memory Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Neo4j Memory Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.