Queue a tenant deletion (R5, 2 approvers). 24h cool-down after approval before
AI agents call tenant_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.
Tenant deletion is a destructive operation that irreversibly removes all associated data, configurations, and context for an entire tenant. Although it includes governance controls (2 approvers, cooldown period), the underlying action cannot be undone and affects all users and data within that tenant scope. This is the most severe category applicable.
From the tool's definition Tool name contains 'delete' and description explicitly states 'tenant deletion' with approval workflow and 24-hour cooldown, indicating irreversible data removal at organizational scope.
Documented attack patterns abuse exactly the kind of access tenant_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 tenant_delete_secure:
{
"version": "1",
"default": "deny",
"hide": [
"tenant_delete_secure"
]
}tenant_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.
Queue a tenant deletion (R5, 2 approvers). 24h cool-down after approval before. 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 tenant_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.
tenant_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 tenant_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 tenant_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.
tenant_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.