// SCAN REPORT

Robust Long-Term Memory MCP

11 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

5 can modify or destroy data

6 read-only

11 tools total

Community server · catalogue entry verified 11/06/2026

How to control Robust Long-Term Memory MCP ↓

TOOL MAP

Read (6) Write / Execute (4) Destructive / Financial (1)

MOST DANGEROUS TOOLS

Critical Risk

Destructive · High delete_memory delete_memory removes data that cannot be undone. Execute · Medium rebuild_vectors Rebuilding a vector index is an Execute-class operation: it runs a repair/reconstruction process that modifies the ChromaDB vector index state. Write · Medium create_backup Creating a backup is a write operation—it generates new data artifacts (backup files). Write · Medium update_memory This tool creates or modifies data (memories) in a reversible manner—an agent could update memory entries but the changes are not permanent/irreversible deletions.

5 of Robust Long-Term Memory MCP's 11 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

HOW TO CONTROL ROBUST LONG-TERM MEMORY MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Robust Long-Term Memory MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_memory": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "remember": {
    "limits": [
      {
        "counter": "remember_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_memory_stats": {
    "limits": [
      {
        "counter": "get_memory_stats_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Robust Long-Term Memory MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ROBUST LONG-TERM MEMORY →

Free to start. No card required.

ALL 11 ROBUST LONG-TERM MEMORY MCP TOOLS

DESTRUCTIVE 1 tools

Destructive delete_memory delete_memory

EXECUTE 1 tools

Execute rebuild_vectors One-time repair: rebuild vector index from SQLite memories.

WRITE 3 tools

Write remember remember Write create_backup create_backup Write update_memory update_memory

READ 6 tools

Read get_memory_stats get_memory_stats Read get_recent_memories get_recent_memories Read search_by_date_range search_by_date_range Read search_by_tags search_by_tags Read search_by_type search_by_type Read search_memories search_memories

RELATED SERVERS

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Can an AI agent delete data through the Robust Long-Term Memory MCP server? +

Yes. The Robust Long-Term Memory MCP server exposes 1 destructive tools including delete_memory. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Robust Long-Term Memory MCP? +

The Robust Long-Term Memory MCP server has 3 write tools including remember, create_backup, update_memory. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Robust Long-Term Memory MCP.

How many tools does the Robust Long-Term Memory MCP server expose? +

11 tools across 3 categories: Destructive, Read, Write. 6 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Robust Long-Term Memory MCP? +

Register the Robust Long-Term Memory MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Robust Long-Term Memory MCP tool call.

Deterministic rules across all 11 Robust Long-Term Memory MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ROBUST LONG-TERM MEMORY →

Free to start. No card required.

11 Robust Long-Term Memory MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

Robust Long-Term Memory MCP

// TOOL MAP

// MOST DANGEROUS TOOLS

// HOW TO CONTROL ROBUST LONG-TERM MEMORY MCP

// ALL 11 ROBUST LONG-TERM MEMORY MCP TOOLS

// RELATED SERVERS

// FAQ