Return the full raw Memory Crystal recall bundle for debugging, including wake, recall, search-messages, recent-messages, and the rendered hook sections.
AI agents call crystal_debug_recall to retrieve information from Memory Crystal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and returns internal memory state and bundled data without modifying or deleting anything. This is a read operation. However, severity is elevated to medium rather than low because the 'full raw' bundle likely exposes sensitive conversation history, extracted knowledge, and internal system state that could be exploited if an agent misuses it—e.g., leaking private user data, previous sessions, or…
From the tool's definition Returns the full raw Memory Crystal recall bundle for debugging, including wake, recall, search-messages, recent-messages, and the rendered hook sections.
Documented attack patterns abuse exactly the kind of access crystal_debug_recall 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_debug_recall:
{
"version": "1",
"default": "deny",
"tools": {
"crystal_debug_recall": {}
}
}crystal_debug_recall is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the full raw Memory Crystal recall bundle for debugging, including wake, recall, search-messages, recent-messages, and the rendered hook sections. It is categorised as a Read tool in the Memory Crystal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Memory Crystal MCP Server MCP server in PolicyLayer and add a rule for crystal_debug_recall: 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_debug_recall is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the crystal_debug_recall 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_debug_recall. 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_debug_recall 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.