Low Risk

lifecycle_status

Show document lifecycle statistics: active, archived, forgotten, pinned, snoozed counts and policy summary.

How to control lifecycle_status ↓

AI agents call lifecycle_status to retrieve information from ClawMem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and displays aggregate statistics about document states (active, archived, forgotten, pinned, snoozed) and policy information. It performs no mutations, deletions, executions, or financial operations. The function is purely informational, making it a straightforward Read category tool with low risk.

From the tool's definition The tool 'Show document lifecycle statistics' with descriptions of counts and summaries indicates data retrieval with no modification.

Documented attack patterns abuse exactly the kind of access lifecycle_status 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_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "lifecycle_status": {}
  }
}

lifecycle_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the lifecycle_status tool do? +

Show document lifecycle statistics: active, archived, forgotten, pinned, snoozed counts and policy summary. It is categorised as a Read tool in the ClawMem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on lifecycle_status? +

Register the ClawMem MCP server in PolicyLayer and add a rule for lifecycle_status: 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_status? +

lifecycle_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit lifecycle_status? +

Yes. Add a rate_limit block to the lifecycle_status 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_status completely? +

Set action: deny in the PolicyLayer policy for lifecycle_status. 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_status? +

lifecycle_status 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.