Delete a saved session Use when native conversation memory is wrong because you need durable cross-session state — restoring agent definitions, swarm topology, memory store, breaker history. For in-session continuation only, no tool needed. Pair with session_save before exiting and session_restor...
AI agents call session_delete to permanently remove resources in Claude Flow — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently destroys durable cross-session state that orchestrates multi-agent swarms and their configurations. Deletion is irreversible and would cause loss of autonomous agent definitions, topology mappings, and operational history. While not financial or directly executable, the destructive nature of removing enterprise orchestration state warrants high severity.
From the tool's definition 'Delete a saved session' — the tool irreversibly removes persistent state including 'agent definitions, swarm topology, memory store, breaker history'. Once deleted, session data cannot be recovered.
Attacks that exploit this kind of access
Delete a saved session Use when native conversation memory is wrong because you need durable cross-session state — restoring agent definitions, swarm topology, memory store, breaker history. For in-session continuation only, no tool needed. Pair with session_save before exiting and session_restore on resume. It is categorised as a Destructive tool in the Claude Flow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claude Flow MCP server in PolicyLayer and add a rule for session_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 Flow. Nothing to install.
session_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 session_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 session_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.
session_delete is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.