memory_bank_delete_project

💥 [DANGER - DELETE PROJECT] Delete an entire project and all its files. ⚠️ EXTREME CAUTION: This action is permanent and cannot be undone. Use only when absolutely certain you want to destroy all project data.

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

What memory_bank_delete_project does on Memory Bank Mcp Mongodb

AI agents call memory_bank_delete_project 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_delete_project needs a policy

This tool permanently and irreversibly deletes all data associated with a project. The description explicitly states the action cannot be undone, meeting the definition of Destructive. The blast radius is critical since an agent misuse could eliminate entire projects of user data with no recovery path. The warning language ('DANGER', 'EXTREME CAUTION') confirms the severe nature.

From the tool's definition 'Delete an entire project and all its files' and 'This action is permanent and cannot be undone' - irreversible data destruction at project scale.

Risk signalsBulk/mass operation — affects multiple targets

Questions about memory_bank_delete_project

What does the memory_bank_delete_project tool do? +

💥 [DANGER - DELETE PROJECT] Delete an entire project and all its files. ⚠️ EXTREME CAUTION: This action is permanent and cannot be undone. Use only when absolutely certain you want to destroy all project data. 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_delete_project? +

Register the Memory Bank Mcp Mongodb MCP server in PolicyLayer and add a rule for memory_bank_delete_project: 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_delete_project? +

memory_bank_delete_project 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_delete_project? +

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

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

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