memory_delete
Delete a technique from the library (creates backup first).
This record as markdown: /tools/io-github-dreamrec-livepilot/memory-delete.md
What memory_delete does on Livepilot
AI agents call memory_delete to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why memory_delete is rated Critical
Although the description mentions 'creates backup first', which provides some mitigation, the core action is deletion of data from a library. This is irreversible in the primary sense (the library entry is removed). Destructive is more severe than Write, as it cannot be undone without manual backup recovery. The backup is a safety measure but does not change the destructive nature of the operation itself.
From the tool's definition Tool name is 'memory_delete' and description states 'Delete a technique from the library'. The verb 'delete' combined with removal from a library indicates irreversible data deletion.
Attacks that exploit this kind of access
The rule that runs memory_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_delete, this is the rule to start with:
memory_delete 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 Livepilot, apply this rule, and every memory_delete call is checked against it from then on.
Questions about memory_delete
Delete a technique from the library (creates backup first). It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Livepilot 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 Livepilot. 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 Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
Across the catalogue