get_decayed_memories
List memories whose importance has fallen below a threshold due to time-based decay. Unlike get_stale_entities (which uses freshness timestamps), this uses decay engine importance calculations.
This record as markdown: /tools/danielsimonjr-memory-mcp/get-decayed-memories.md
What get_decayed_memories does on Enhanced Knowledge Graph Memory Server
AI agents call get_decayed_memories to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_decayed_memories is rated Low
This tool retrieves and queries stored memories based on a decay threshold without creating, modifying, deleting, or executing any operations. It is purely informational, returning a filtered view of existing data. No side effects or irreversible actions occur.
From the tool's definition Tool description states it 'List memories' and 'uses decay engine importance calculations' to filter results. The verb 'list' and the retrieval-only nature (no modification, deletion, or execution) align with Read category semantics.
Attacks that exploit this kind of access
The rule that runs get_decayed_memories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_decayed_memories, this is the rule to start with:
get_decayed_memories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every get_decayed_memories call is checked against it from then on.
Questions about get_decayed_memories
List memories whose importance has fallen below a threshold due to time-based decay. Unlike get_stale_entities (which uses freshness timestamps), this uses decay engine importance calculations. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for get_decayed_memories: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
get_decayed_memories 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 get_decayed_memories 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 get_decayed_memories. 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.
get_decayed_memories is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue