delete_memory

Permanently delete a memory. Use when the user explicitly asks to forget something, or when a memory is clearly outdated and no longer relevant. Search for the memory first if you don

Server Memsolus MCP Server memsolus/mcp
Category Destructive
Risk class Critical
Parameters 00 required

What delete_memory does on Memsolus MCP Server

AI agents call delete_memory to permanently remove resources in Memsolus MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_memory needs a policy

This tool irreversibly removes stored data (memories) from the agent's persistent knowledge store. Once deleted, the memory cannot be recovered. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is somewhat limited to the agent's own memory system rather than external data, the permanent nature of the deletion and…

From the tool's definition Tool name is 'delete_memory' with description stating 'Permanently delete a memory.' The use of 'Permanently delete' indicates an irreversible action that cannot be undone.

Questions about delete_memory

What does the delete_memory tool do? +

Permanently delete a memory. Use when the user explicitly asks to forget something, or when a memory is clearly outdated and no longer relevant. Search for the memory first if you don. It is categorised as a Destructive tool in the Memsolus MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_memory? +

Register the Memsolus MCP Server 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 Memsolus MCP Server. Nothing to install.

What risk level is delete_memory? +

delete_memory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_memory? +

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.

How do I block delete_memory completely? +

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.

What MCP server provides delete_memory? +

delete_memory is provided by the Memsolus MCP Server MCP server (memsolus/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.