update_memory

THE RISK

Medium Risk

Why update_memory needs a policy

This tool modifies existing memory records by updating their properties, which is a reversible Write operation. It does not create new data (Write but less invasive than create_memory), does not delete data (which would be Destructive), and does not execute arbitrary code or commands (Execute).

From the tool's definition Tool name 'update_memory' and description 'Update properties of an existing memory' indicates modification of existing data in the Neo4j graph database. The verb 'update' is a classic Write operation that reversibly modifies data.

Documented attack patterns abuse exactly the kind of access update_memory gives an agent:

POLICY

How to control update_memory

PolicyLayer is an MCP gateway — it sits between your AI agents and Neo4j Agent Memory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_memory:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_memory": {
      "limits": [
        {
          "counter": "update_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_memory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

Create a free account and register Neo4j Agent Memory MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Neo4j Agent Memory MCP Server tools

Destructive delete_connection Delete a specific connection between two memories Destructive delete_memory Delete a memory and all its connections Write create_connection Create a connection between two memories (it Write create_memory Create a new memory in the knowledge graph (remember to connect it to related memories). C Write update_connection Update properties of an existing connection between memories Read get_guidance Get help on using the memory tools effectively Read list_memory_labels List all unique memory labels currently in use with their counts Read search_memories Search and retrieve memories from the knowledge graph

All 9 Neo4j Agent Memory MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_memory

What does the update_memory tool do? +

Update properties of an existing memory. It is categorised as a Write tool in the Neo4j Agent Memory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_memory? +

Register the Neo4j Agent Memory MCP Server MCP server in PolicyLayer and add a rule for update_memory: 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 Agent Memory MCP Server. Nothing to install.

What risk level is update_memory? +

update_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_memory? +

Yes. Add a rate_limit block to the update_memory 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.

How do I block update_memory completely? +

Set action: deny in the PolicyLayer policy for update_memory. 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.

What MCP server provides update_memory? +

update_memory is provided by the Neo4j Agent Memory MCP Server MCP server (knowall-ai/mcp-neo4j-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Neo4j Agent Memory MCP Server tool call.

Start from Neo4j Agent Memory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →