Get the evolution timeline for a memory document, showing how its keywords and context have changed over time based on new evidence.
AI agents call memory_evolution_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.
This tool retrieves and displays the evolution history of a memory document's keywords and context. It is purely informational—no data is created, modified, deleted, or executed. The operation is read-only with no side effects or blast radius if misused by an AI agent.
From the tool's definition Tool name 'memory_evolution_status' and description 'Get the evolution timeline' indicate a retrieval operation.
Documented attack patterns abuse exactly the kind of access memory_evolution_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 memory_evolution_status:
{
"version": "1",
"default": "deny",
"tools": {
"memory_evolution_status": {}
}
}memory_evolution_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the evolution timeline for a memory document, showing how its keywords and context have changed over time based on new evidence. It is categorised as a Read tool in the ClawMem MCP Server, which means it retrieves data without modifying state.
Register the ClawMem MCP server in PolicyLayer and add a rule for memory_evolution_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.
memory_evolution_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the memory_evolution_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.
Set action: deny in the PolicyLayer policy for memory_evolution_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.
memory_evolution_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.
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.