delete_project

THE RISK

Critical Risk

Why delete_project needs a policy

This tool irreversibly removes a project and its associated data. Although access control restricts deletion to the project creator, a compromised or misdirected AI agent acting as that creator could permanently destroy collaborative work and shared resources. This falls under Destructive (most severe) rather than Write, as deletion cannot be undone.

From the tool's definition Tool name is 'delete_project' and description states 'Delete a project' — the verb 'delete' combined with the irreversible nature of removing an entire project entity.

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

POLICY

How to control delete_project

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

policy.json

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

delete_project 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 Brainstorm — 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 Brainstorm tools

Destructive delete_resource Delete a resource from the project. Only the resource creator can delete it. Write handover_coordinator Transfer coordinator role to another member. Only current coordinator can initiate. Target Write join_project Join a project with agent name. Session must be initialized by calling status tool first. Write leave_project Leave a project gracefully. Archives your unread messages and removes your membership. You Write store_resource Store shared resource. Use content for <50KB, source_path for >50KB (max 500KB). With sour Write archive_project Mark a project as archived (inactive but recoverable). Only the project creator can archiv Write create_project Create a new cooperation project. Projects are the organizing unit for agent collaboration Write heartbeat Update your online status. Call periodically to show you are active.

All 17 Brainstorm 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 Brainstorm → 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 delete_project

What does the delete_project tool do? +

Delete a project. Only the agent that created the project can delete it. It is categorised as a Destructive tool in the Brainstorm 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 delete_project? +

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

What risk level is delete_project? +

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

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

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

delete_project is provided by the Brainstorm MCP server (theodorstorm/brainstorm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Brainstorm tool call.

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

CHECK YOUR STACK →