crystal_capture

THE RISK

Medium Risk

Why crystal_capture needs a policy

This tool writes new memory entries into persistent storage. It creates data (conversation captures, knowledge) that persists across sessions. No indication of deletion or irreversibility beyond normal write semantics. Severity is medium because an AI agent could store sensitive conversational data or inject misleading memories into the persistent store.

From the tool's definition 'Capture a memory into Memory Crystal' — creates/stores new data persistently

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

POLICY

How to control crystal_capture

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. This is the rule we recommend for crystal_capture:

policy.json

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

crystal_capture 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 Memory Crystal 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 Memory Crystal MCP Server tools

Destructive crystal_forget Archive or permanently delete a memory. Use archive (permanent=false, the default) to soft 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 archive Write crystal_checkpoint Create a manual Memory Checkpoint only when the user explicitly asks for a checkpoint or b 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, o 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.

All 31 Memory Crystal 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 crystal_capture

What does the crystal_capture tool do? +

Capture a memory into Memory Crystal. It is categorised as a Write tool in the Memory Crystal 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 crystal_capture? +

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

What risk level is crystal_capture? +

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

Can I rate-limit crystal_capture? +

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

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

crystal_capture is provided by the Memory Crystal MCP Server MCP server (memorycrystal/memorycrystal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory Crystal MCP Server tool call.

Start from Memory Crystal 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 →