Clear data from the graph. SAFETY: To clear all data, you MUST explicitly pass type=
AI agents call memory_clear to permanently remove resources in M I M I R Multi Agent Intelligent Memory & Insight Repository — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes data from a persistent Neo4j graph database. Clearing graph data is irreversible and cannot be recovered without backups. While the safety mechanism requires explicit parameters, the tool's core function is to permanently delete information.
From the tool's definition Tool name is 'memory_clear' and description states 'Clear data from the graph.' The word 'clear' combined with operation on a persistent graph database constitutes irreversible deletion.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access memory_clear gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M I M I R Multi Agent Intelligent Memory & Insight Repository, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_clear:
{
"version": "1",
"default": "deny",
"hide": [
"memory_clear"
]
}memory_clear disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
All 13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools →
Clear data from the graph. SAFETY: To clear all data, you MUST explicitly pass type=. It is categorised as a Destructive tool in the M I M I R Multi Agent Intelligent Memory & Insight Repository MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the M I M I R Multi Agent Intelligent Memory & Insight Repository MCP server in PolicyLayer and add a rule for memory_clear: 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 M I M I R Multi Agent Intelligent Memory & Insight Repository. Nothing to install.
memory_clear is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the memory_clear 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 memory_clear. 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.
memory_clear is provided by the M I M I R Multi Agent Intelligent Memory & Insight Repository MCP server (orneryd/mimir). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 M I M I R Multi Agent Intelligent Memory & Insight Repository tools catalogued and risk-classified — across an index of 42,500+ MCP servers.