memory_bank_cleanup_old_versions

🧹 [MAINTENANCE] Clean up old file versions to save storage space. Keeps recent versions and removes older ones. Use periodically for maintenance. Default keeps 10 versions per file.

Server Memory Bank Mcp Mongodb sato-isolated/memory-bank-mcp-mongo
Category Destructive
Risk class Critical
Parameters 00 required

What memory_bank_cleanup_old_versions does on Memory Bank Mcp Mongodb

AI agents call memory_bank_cleanup_old_versions to permanently remove resources in Memory Bank Mcp Mongodb — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why memory_bank_cleanup_old_versions needs a policy

This tool irreversibly removes old file versions from storage. Once deleted, those historical versions are gone permanently. While it preserves recent versions, the removal of older ones is a destructive, non-reversible operation. The blast radius is high because an AI agent could misconfigure the retention count (e.g., keep only 1 version) and wipe out significant version history across all files in a project.

From the tool's definition 'Clean up old file versions' and 'removes older ones' — permanently deletes historical version data that cannot be recovered

Questions about memory_bank_cleanup_old_versions

What does the memory_bank_cleanup_old_versions tool do? +

🧹 [MAINTENANCE] Clean up old file versions to save storage space. Keeps recent versions and removes older ones. Use periodically for maintenance. Default keeps 10 versions per file. It is categorised as a Destructive tool in the Memory Bank Mcp Mongodb 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 memory_bank_cleanup_old_versions? +

Register the Memory Bank Mcp Mongodb MCP server in PolicyLayer and add a rule for memory_bank_cleanup_old_versions: 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 Memory Bank Mcp Mongodb. Nothing to install.

What risk level is memory_bank_cleanup_old_versions? +

memory_bank_cleanup_old_versions 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 memory_bank_cleanup_old_versions? +

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

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

memory_bank_cleanup_old_versions is provided by the Memory Bank Mcp Mongodb MCP server (sato-isolated/memory-bank-mcp-mongo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.