Bulk-delete memories with scope-driven approval gating. <100 rows → R3 confirm,
AI agents call memory_bulk_delete_secure to permanently remove resources in Celiums Memory — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes memory records, which cannot be reversed. Even with approval gating, bulk deletion of cognitive memory data represents a destructive operation with significant blast radius if misused by an AI agent (e.g., wiping out user memory contexts, project histories, or knowledge modules). Destructive severity is appropriate over Write because the action is irreversible.
From the tool's definition Tool name includes 'bulk_delete' and description states 'Bulk-delete memories' — this irreversibly removes data in bulk quantities.
Documented attack patterns abuse exactly the kind of access memory_bulk_delete_secure gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Celiums Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_bulk_delete_secure:
{
"version": "1",
"default": "deny",
"hide": [
"memory_bulk_delete_secure"
]
}memory_bulk_delete_secure disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Bulk-delete memories with scope-driven approval gating. <100 rows → R3 confirm,. It is categorised as a Destructive tool in the Celiums Memory MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Celiums Memory MCP server in PolicyLayer and add a rule for memory_bulk_delete_secure: 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 Celiums Memory. Nothing to install.
memory_bulk_delete_secure 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_bulk_delete_secure 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_bulk_delete_secure. 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_bulk_delete_secure is provided by the Celiums Memory MCP server (terrizoaguimor/celiums-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Celiums Memory, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
62 Celiums Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.