Restore documents that were auto-archived by lifecycle policies. Does NOT restore manually forgotten documents.
AI agents use lifecycle_restore to create or update resources in ClawMem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClawMem environment.
This tool modifies the lifecycle state of documents by moving them from archived back to active status. This is a Write operation (reversible state change) rather than Read (it actively changes data) or Destructive (restoration is not permanent destruction).
From the tool's definition Tool performs 'Restore' operation on auto-archived documents, reversibly reactivating data that was moved to archived state. The description explicitly states it restores documents, which is a modification operation that changes the state/location of data.
Documented attack patterns abuse exactly the kind of access lifecycle_restore 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_restore:
{
"version": "1",
"default": "deny",
"tools": {
"lifecycle_restore": {
"limits": [
{
"counter": "lifecycle_restore_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}lifecycle_restore stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Restore documents that were auto-archived by lifecycle policies. Does NOT restore manually forgotten documents. It is categorised as a Write tool in the ClawMem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ClawMem MCP server in PolicyLayer and add a rule for lifecycle_restore: 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.
lifecycle_restore is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lifecycle_restore 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 lifecycle_restore. 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.
lifecycle_restore 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.
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.