Critical Risk →

lifecycle_sweep

Run lifecycle policies: archive stale docs, optionally purge old archives. Defaults to dry_run (preview only).

How to control lifecycle_sweep ↓

AI agents call lifecycle_sweep to permanently remove resources in ClawMem — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Although the tool defaults to dry-run mode (mitigating the risk), the actual operational mode purges and archives data irreversibly. This is Destructive rather than Write because the effects cannot be undone—archived or purged documents are lost from the primary store.

From the tool's definition 'purge old archives' and 'archive stale docs' indicate irreversible deletion or removal of data. The tool description explicitly mentions the ability to purge, which constitutes permanent data loss.

Documented attack patterns abuse exactly the kind of access lifecycle_sweep gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ClawMem, and nothing reaches the server without passing your rules. This is the rule we recommend for lifecycle_sweep:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "lifecycle_sweep"
  ]
}

lifecycle_sweep disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register ClawMem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the lifecycle_sweep tool do? +

Run lifecycle policies: archive stale docs, optionally purge old archives. Defaults to dry_run (preview only). It is categorised as a Destructive tool in the ClawMem MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on lifecycle_sweep? +

Register the ClawMem MCP server in PolicyLayer and add a rule for lifecycle_sweep: 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 ClawMem. Nothing to install.

What risk level is lifecycle_sweep? +

lifecycle_sweep is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit lifecycle_sweep? +

Yes. Add a rate_limit block to the lifecycle_sweep 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.

How do I block lifecycle_sweep completely? +

Set action: deny in the PolicyLayer policy for lifecycle_sweep. 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.

What MCP server provides lifecycle_sweep? +

lifecycle_sweep is provided by the ClawMem MCP server (yoloshii/clawmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ClawMem tool call.

Deterministic rules across all 30 ClawMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 ClawMem tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.