cleanup_expired_working_memory

THE RISK

Critical Risk

Why cleanup_expired_working_memory needs a policy

Cleaning up expired working memories implies irreversible deletion of memory records. Although they are 'expired' (suggesting they may be low-value), the operation cannot be undone and permanently removes data from the persistent memory system. This qualifies as Destructive. Severity is medium because the affected data is expired/stale, limiting the blast radius compared to deleting active memories.

From the tool's definition 'Clean up expired working memories' — removes/deletes memory entries that have expired

Documented attack patterns abuse exactly the kind of access cleanup_expired_working_memory gives an agent:

POLICY

How to control cleanup_expired_working_memory

PolicyLayer is an MCP gateway — it sits between your AI agents and AGI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanup_expired_working_memory:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cleanup_expired_working_memory"
  ]
}

cleanup_expired_working_memory disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register AGI MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AGI MCP Server tools

Destructive prune_memories Permanently delete memories based on criteria Write consolidate_working_memory Consolidate multiple working memories into a single semantic memory Write activate_cluster Activate a memory cluster and get its associated memories Write archive_old_memories Archive old memories based on age and importance criteria Write create_memory Create a new memory with optional type-specific metadata Write create_memory_cluster Create a new memory cluster Write create_memory_relationship Create a relationship between two memories Write create_working_memory Create a temporary working memory with expiration

All 24 AGI MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in AGI MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cleanup_expired_working_memory

What does the cleanup_expired_working_memory tool do? +

Clean up expired working memories. It is categorised as a Destructive tool in the AGI MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_expired_working_memory? +

Register the AGI MCP Server MCP server in PolicyLayer and add a rule for cleanup_expired_working_memory: 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 AGI MCP Server. Nothing to install.

What risk level is cleanup_expired_working_memory? +

cleanup_expired_working_memory is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_expired_working_memory? +

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

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

cleanup_expired_working_memory is provided by the AGI MCP Server MCP server (quixiai/agi-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AGI MCP Server tool call.

Start from AGI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →