Critical-risk tools in Celiums Memory

Critical severity Celiums Memory MCP Server 5 of 62 tools

5 of the 62 tools in Celiums Memory are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.

Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.

Tools at critical risk

forget Destructive

Delete specific memories by ID. Requires explicit IDs — will not bulk delete.
memory_bulk_delete_secure Destructive

Bulk-delete memories with scope-driven approval gating. <100 rows → R3 confirm,
memory_delete_secure Destructive

Delete one or more memories with full security gating (RBAC + AAL + audit).
research_source_delete Destructive

Delete a source (and its chunks) from a research project.
tenant_delete_secure Destructive

Queue a tenant deletion (R5, 2 approvers). 24h cool-down after approval before

Attacks that target this class

Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.

Destructive Action Autonomy
Privilege escalation via admin-only tools
Data exfiltration via tool chaining
Runaway Tool Loops

Critical-risk tools in Celiums Memory

Tools at critical risk

Attacks that target this class

More on Celiums Memory

Enforce policy on every Celiums Memory tool call.