delete-stream
AI agents call delete-stream to permanently remove resources in mem0 MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on memory streams. Given the context of a memory management system where streams store user data, deletion cannot be undone. This is categorized as Destructive (highest applicable severity before Financial) due to the permanent loss of data. High confidence despite empty description because the verb 'delete' is unambiguous in its destructive intent.
From the tool's definition Tool name 'delete-stream' with prefix 'delete' indicates irreversible removal of data. The empty description prevents confirmation of recovery mechanisms, but the semantic meaning is unambiguous.
Attacks that exploit this kind of access
delete-stream. It is categorised as a Destructive tool in the mem0 MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the mem0 MCP Server MCP server in PolicyLayer and add a rule for delete-stream: 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 mem0 MCP Server. Nothing to install.
delete-stream 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-stream 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-stream. 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-stream is provided by the mem0 MCP Server MCP server (sadiuysal/mem0-mcp-server-ts). 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 →