Delete a long-term memory from this MCP session namespace.
AI agents call memory.delete to permanently remove resources in ForLoop MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs deletion of stored memory records, which is an irreversible operation that cannot be undone. Even though the scope is limited to session-namespace memory (not production data), the destructive nature of permanent deletion from persistent storage and the potential loss of important session context or decision records justifies the Destructive category.
From the tool's definition Tool name 'memory.delete' with description 'Delete a long-term memory from this MCP session namespace' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a long-term memory from this MCP session namespace. It is categorised as a Destructive tool in the ForLoop MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ForLoop 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 ForLoop MCP. 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 ForLoop MCP server (master0ffate/forloop-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 →