add_memory · Mem0 MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_memory does on Mem0 MCP Server

AI agents use add_memory to create or update resources in Mem0 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mem0 MCP Server environment.

WHY IT NEEDS A POLICY

Why add_memory needs a policy

This tool creates new memory entries by storing user preferences, facts, or conversation snippets. It is reversible (can be deleted via delete_memory or delete_all_memories shown in sibling tools), has no destructive capability, and does not execute code or move money.

From the tool's definition Tool description states 'Store a new preference, fact, or conversation snippet', which is a create/write operation. The verb 'Store' and action of adding data without deletion or code execution indicate a Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_memory Rate-limited

add_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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mem0 MCP Server, so you can run agents against it safely.

FAQ

Questions about add_memory

What does the add_memory tool do? +

Store a new preference, fact, or conversation snippet. Requires at least one: user_id, agent_id, or run_id. It is categorised as a Write tool in the Mem0 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 add_memory? +

Register the Mem0 MCP Server MCP server in PolicyLayer and add a rule for add_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 Mem0 MCP Server. Nothing to install.

What risk level is add_memory? +

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

Can I rate-limit add_memory? +

Yes. Add a rate_limit block to the add_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 add_memory completely? +

Set action: deny in the PolicyLayer policy for add_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 add_memory? +

add_memory is provided by the Mem0 MCP Server MCP server (mem0ai/mem0-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

add_memory is one line of Mem0 MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →