Create a Memory Crystal memory using semantic embedding + vector storage.
AI agents use crystal_remember to create or update resources in Memory Crystal MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory Crystal MCP Server environment.
This tool writes/creates new memory entries in persistent storage. It is reversible (can be edited or forgotten via sibling tools), so it does not qualify as Destructive. The blast radius is medium: an AI agent could create false, misleading, or sensitive memories that corrupt the knowledge base or pollute future context injections, but the data itself can be undone.
From the tool's definition Tool description states 'Create a Memory Crystal memory using semantic embedding + vector storage' — the verb 'Create' indicates data creation. The sibling tool list includes 'crystal_forget' and 'crystal_edit', confirming this server modifies stored data.
Documented attack patterns abuse exactly the kind of access crystal_remember gives an agent:
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_remember:
{
"version": "1",
"default": "deny",
"tools": {
"crystal_remember": {
"limits": [
{
"counter": "crystal_remember_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} crystal_remember 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.
Free to start. No card required.
Create a Memory Crystal memory using semantic embedding + vector storage. 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.
Register the Memory Crystal MCP Server MCP server in PolicyLayer and add a rule for crystal_remember: 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.
crystal_remember is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crystal_remember 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.
Set action: deny in the PolicyLayer policy for crystal_remember. 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.
crystal_remember 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.
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.
Free to start. No card required.
31 Memory Crystal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.