// SCAN REPORT

Memory Crystal MCP Server

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

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

Last updated: 12 Jun 2026

11 can modify or destroy data

20 read-only

31 tools total

Community server · catalogue entry verified 12/06/2026

How to control Memory Crystal MCP Server ↓

TOOL MAP

What Memory Crystal MCP Server exposes to your agents

Read (20) Write / Execute (10) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Memory Crystal MCP Server tools

Destructive · High crystal_forget This tool can permanently erase memories/data that cannot be recovered (permanent=false toggles behavior, but permanent=true performs irreversible deletion). Write · Medium crystal_checkpoint This tool writes/creates persistent memory checkpoints. Write · Medium crystal_create_knowledge_base This tool creates a new knowledge base, which is a Write operation that establishes persistent data structures. Write · Medium crystal_edit This tool modifies existing data (memory records) in a reversible manner.

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

POLICY

How to control Memory Crystal MCP Server

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

Deny destructive operations

{
  "crystal_forget": {
    "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

{
  "crystal_capture": {
    "limits": [
      {
        "counter": "crystal_capture_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "crystal_doctor": {
    "limits": [
      {
        "counter": "crystal_doctor_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 Memory Crystal MCP Server — 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 MEMORY CRYSTAL →

Free to start. No card required.

FULL CATALOGUE

All 31 Memory Crystal MCP Server tools

DESTRUCTIVE 1 tools

Destructive crystal_forget Archive or permanently delete a memory. Use archive (permanent=false, the default) to soft-delete so the memor

WRITE 10 tools

Write crystal_capture Capture a memory into Memory Crystal Write crystal_idea_action Take action on a memory discovery -- star it as valuable, dismiss it, or mark it as read. Write crystal_supersede Atomically replace a stale or incorrect memory with a successor. The old memory is archived and linked to the Write crystal_checkpoint Create a manual Memory Checkpoint only when the user explicitly asks for a checkpoint or backup. Checkpoints a Write crystal_create_knowledge_base Create a Memory Crystal knowledge base. Write crystal_edit Update an existing memory in Memory Crystal. Use to correct errors, add new information, or update the status Write crystal_import_knowledge Import text chunks into a Memory Crystal knowledge base. Write crystal_remember Create a Memory Crystal memory using semantic embedding + vector storage. Write crystal_set_scope Override Memory Crystal channel scope for the current session. Write crystal_update Update an existing Memory Crystal memory in place. Use to correct or enrich a memory when it remains the same

READ 20 tools

Read crystal_doctor Run a health check on the Memory Crystal plugin: verify config, connectivity, and backend status. Read crystal_debug_recall Return the full raw Memory Crystal recall bundle for debugging, including wake, recall, search-messages, recen Read crystal_dependency_chain Trace the dependency chain for a goal, project, or task in your knowledge graph. Returns a tree of dependencie Read crystal_explain_connection Explain how two entities are connected in your knowledge graph. Returns direct relationships, indirect paths, Read crystal_ideas View recent discoveries your memory has made -- cross-memory connections, patterns, and insights found between Read crystal_list_knowledge_bases List available Memory Crystal knowledge bases. Read crystal_query_knowledge_base Search within a specific Memory Crystal knowledge base. Read crystal_recall Recall memories from Memory Crystal Read crystal_recent crystal_recent Read crystal_search_messages crystal_search_messages Read crystal_stats Get Memory Crystal stats Read crystal_status Show Memory Crystal plugin status, version, backend connectivity, and runtime counters. Read crystal_trace Trace a memory back to its source conversation. Use when you need to understand where a memory came from or ve Read crystal_wake Get wake briefing for a channel/session Read crystal_what_do_i_know Broad topic scan over Memory Crystal memories. Read crystal_who_owns Find who owns, manages, or is assigned to an entity in your knowledge graph. Returns ownership chains and evid Read crystal_why_did_we Decision archaeology across Memory Crystal decision memories. Read memory_get Read a full saved memory item by memoryId or crystal/<id>.md path. Read memory_search Search saved memory for relevant long-term context. Returns crystal/<id>.md paths for use with memory_get. Read crystal_preflight ALWAYS call this before any config change, API write, file deletion, external message send, or production syst

EXPLORE

Related servers

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

FAQ

Questions about Memory Crystal MCP Server

Can an AI agent delete data through the Memory Crystal MCP Server MCP server? +

Yes. The Memory Crystal MCP Server server exposes 1 destructive tools including crystal_forget. 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 Memory Crystal MCP Server? +

The Memory Crystal MCP Server server has 10 write tools including crystal_capture, crystal_idea_action, crystal_supersede. 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 Memory Crystal MCP Server.

How many tools does the Memory Crystal MCP Server MCP server expose? +

31 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on Memory Crystal MCP Server? +

Register the Memory Crystal MCP Server 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 Memory Crystal MCP Server tool call.

Deterministic rules across all 31 Memory Crystal MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MEMORY CRYSTAL →

Free to start. No card required.

31 Memory Crystal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.