DECAY STATUS LIFECYCLE STATE - Get decay status and lifecycle information for a memory including state, decay score, and preservation status. Keywords: decay, status, lifecycle, state, age, freshness, preservation, expiry
AI agents call memory_decay_status to retrieve information from MCP AI Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about memory objects (decay score, lifecycle state, preservation status) without creating, modifying, deleting, executing code, or affecting financial state. It is a pure read operation analogous to a 'get' or 'status' query. The blast radius of misuse is minimal — an agent could only retrieve information about its own memory state, posing no data integrity or operational risk.
From the tool's definition Tool name 'memory_decay_status' and description explicitly states 'Get decay status and lifecycle information' — a retrieval operation with no modification or side effects. Keywords include 'status', 'state', 'age', 'freshness' indicating read-only querying.
Documented attack patterns abuse exactly the kind of access memory_decay_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP AI Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_decay_status:
{
"version": "1",
"default": "deny",
"tools": {
"memory_decay_status": {}
}
}memory_decay_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.
DECAY STATUS LIFECYCLE STATE - Get decay status and lifecycle information for a memory including state, decay score, and preservation status. Keywords: decay, status, lifecycle, state, age, freshness, preservation, expiry. It is categorised as a Read tool in the MCP AI Memory MCP Server, which means it retrieves data without modifying state.
Register the MCP AI Memory MCP server in PolicyLayer and add a rule for memory_decay_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 MCP AI Memory. Nothing to install.
memory_decay_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_decay_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_decay_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_decay_status is provided by the MCP AI Memory MCP server (scanadi/mcp-ai-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 MCP AI Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 MCP AI Memory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.