run_decay_cycle

Run a single pass of time-based importance decay across all agent memories. Returns count of decayed and forgotten memories.

SERVEREnhanced Knowledge Graph Memory Server SOURCEdanielsimonjr/memory-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/danielsimonjr-memory-mcp/run-decay-cycle.md

WHAT IT DOES

What run_decay_cycle does on Enhanced Knowledge Graph Memory Server

AI agents invoke run_decay_cycle to trigger actions in Enhanced Knowledge Graph Memory Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_decay_cycle is rated High

This tool executes a decay operation across all memories, modifying importance levels and potentially causing memories to be 'forgotten' (removed or deprioritized). While it may not permanently delete records, it triggers a bulk automated operation with side effects on all agent memories. The scope (all memories) and irreversibility of decay/forgetting makes this high severity.

From the tool's definition 'Run a single pass of time-based importance decay across all agent memories' and 'Returns count of decayed and forgotten memories'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_decay_cycle 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 run_decay_cycle, this is the rule to start with:

run_decay_cycle Rate-limited

run_decay_cycle stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_decay_cycle": {
      "limits": [
        {
          "counter": "run_decay_cycle_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every run_decay_cycle call is checked against it from then on.

FAQ

Questions about run_decay_cycle

What does the run_decay_cycle tool do? +

Run a single pass of time-based importance decay across all agent memories. Returns count of decayed and forgotten memories. It is categorised as a Execute tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_decay_cycle? +

Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for run_decay_cycle: 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.

What risk level is run_decay_cycle? +

run_decay_cycle is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_decay_cycle? +

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

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

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

KEEP EXPLORING

More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.

This server

All 225 Enhanced Knowledge Graph Memory Server tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →