메모리 삭제. 관련 임베딩도 함께 삭제됩니다.
AI agents call memory_delete to permanently remove resources in Claude Session Continuity — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes memory entries and their associated embeddings without apparent recovery mechanism. Data deletion is irreversible and represents the most severe category. While the blast radius depends on what memories exist in a given session, the destructive nature of permanent data removal justifies 'high' severity.
From the tool's definition Tool name is 'memory_delete' and description states '메모리 삭제' (memory delete). The description explicitly indicates '관련 임베딩도 함께 삭제됩니다' (related embeddings will also be deleted together), confirming irreversible deletion of data.
Attacks that exploit this kind of access
메모리 삭제. 관련 임베딩도 함께 삭제됩니다. It is categorised as a Destructive tool in the Claude Session Continuity MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for memory_delete: 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 Claude Session Continuity. Nothing to install.
memory_delete 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 memory_delete 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 memory_delete. 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.
memory_delete is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →