delete_memory

Permanently delete a memory by ID. Use archive_memory instead for soft delete.

SERVERCognio SOURCE0xrelogic/cognio
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/0xrelogic-cognio/delete-memory.md

What delete_memory does on Cognio

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

Why delete_memory is rated Critical

This tool irreversibly deletes data (memory records) and cannot be undone. The description explicitly contrasts it with a reversible alternative (archive_memory), confirming permanent deletion semantics. An AI agent misusing this could erase important contextual information or user data without recovery.

From the tool's definition Tool name is 'delete_memory' and description states 'Permanently delete a memory by ID' with explicit acknowledgment that this is irreversible ('Use archive_memory instead for soft delete').

Questions about delete_memory

What does the delete_memory tool do? +

Permanently delete a memory by ID. Use archive_memory instead for soft delete. It is categorised as a Destructive tool in the Cognio 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 Cognio 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 Cognio. 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 Cognio MCP server (0xrelogic/cognio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Cognio, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Cognio's. Pull the full record:

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.