Delete a memory by name. Pass workspace to disambiguate if the name exists in multiple workspaces.
AI agents call delete_memory to permanently remove resources in Memlord — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes stored memory records. Although the blast radius is limited to personal/team memory data rather than critical infrastructure or financial systems, the permanent and unrecoverable nature of deletion—combined with the lack of described safeguards like soft-deletes, backups, or confirmation prompts—makes this a Destructive category risk.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete a memory by name'. The verb 'delete' indicates irreversible removal of data.
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 Memlord, 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 a memory by name. Pass workspace to disambiguate if the name exists in multiple workspaces. It is categorised as a Destructive tool in the Memlord MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Memlord 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 Memlord. 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 Memlord MCP server (myrikld/memlord). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memlord, 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.
10 Memlord tools catalogued and risk-classified — across an index of 43,000+ MCP servers.