This record as markdown: /tools/dev-aic0rt3x-memory-mcp/delete-memory.md
What delete_memory does on AI Cortex Storage
AI agents call delete_memory to permanently remove resources in AI Cortex Storage, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | ≤ 255 characters, no '/' |
namespace | string | Yes | ≤ 255 characters, no '/' |
Parameters from the server's own tool schema.
Why delete_memory is rated Critical
This tool permanently removes stored data from persistent cloud memory. Deletion is irreversible and cannot be undone. While the blast radius depends on what memories are targeted, the capability to irreversibly erase AI agent memories—potentially including important context, decisions, or session data—represents a high-severity destructive action.
From the tool's definition Tool name is 'delete_memory' and description states 'Delete a stored value.' The verb 'Delete' combined with operation on persistent cloud memory indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_memory, this is the rule to start with:
delete_memory is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AI Cortex Storage, apply this rule, and every delete_memory call is checked against it from then on.
Questions about delete_memory
Delete a stored value. It is categorised as a Destructive tool in the AI Cortex Storage MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_memory accepts 2 parameters: key, namespace. Required: key, namespace. The full parameter table on this page comes from the server's own tool schema.
Register the AI Cortex Storage 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 AI Cortex Storage. 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 AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Cortex Storage, and thousands of servers like it.
Across the catalogue