import_memories · r3 (Recall) MCP: Risk & Policy

WHAT IT DOES

What import_memories does on r3 (Recall)

AI agents use import_memories to create or update resources in r3 (Recall) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your r3 (Recall) environment.

WHY IT NEEDS A POLICY

Why import_memories needs a policy

Import operations create and persist new data records in the memory system. While reversible (memories can be deleted via delete_memory tool), bulk imports can introduce large volumes of data and potentially overwrite or corrupt existing memories if duplicates aren't handled properly.

From the tool's definition Tool performs 'bulk import' operation that creates or adds memories to the storage system. Description explicitly states it imports from external sources (mem0 API or JSON file), which constitutes data creation/modification rather than retrieval.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

import_memories Rate-limited

import_memories 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": {
    "import_memories": {
      "limits": [
        {
          "counter": "import_memories_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 r3 (Recall), so you can run agents against it safely.

FAQ

Questions about import_memories

What does the import_memories tool do? +

Bulk import memories from mem0 API or JSON file. It is categorised as a Write tool in the r3 (Recall) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_memories? +

Register the r3 (Recall) MCP server in PolicyLayer and add a rule for import_memories: 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 r3 (Recall). Nothing to install.

What risk level is import_memories? +

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

Can I rate-limit import_memories? +

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

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

import_memories is provided by the r3 (Recall) MCP server (n3wth/r3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.