AI agents call delete_memory to permanently remove resources in Memory-Plus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the empty description, the tool name combined with the server's stated purpose ('recording, retrieval, updating, and visualization of persistent memories') makes it clear this tool deletes memory entries irreversibly. Deletion of persistent data cannot be undone and qualifies as Destructive. The high confidence reflects the unambiguous naming convention, though the empty description prevents 100% certainty.
From the tool's definition Tool named 'delete_memory' with empty description. Sibling tools include 'delete', 'record_memory', 'update', and 'retrieve_memory', establishing this server's purpose is memory management.
Documented attack patterns abuse exactly the kind of access delete_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory-Plus, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_memory:
{
"version": "1",
"default": "deny",
"hide": [
"delete_memory"
]
}delete_memory 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.
delete_memory. It is categorised as a Destructive tool in the Memory-Plus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memory-Plus MCP server in PolicyLayer and add a rule for delete_memory: 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-Plus. Nothing to install.
delete_memory 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 delete_memory 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 delete_memory. 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.
delete_memory is provided by the Memory-Plus MCP server (yuchen20/memory-plus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Memory-Plus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 Memory-Plus tools catalogued and risk-classified — across an index of 42,500+ MCP servers.