cleanup_empty_projects

THE RISK

Critical Risk

Why cleanup_empty_projects needs a policy

While the tool only targets empty projects (no memory contexts), the optional deletion path is irreversible. The blast radius is medium because only projects with no contexts are affected, reducing the risk of significant data loss, but the deletion action itself is permanent and cannot be undone.

From the tool's definition 'optionally deletes them' — the tool can irreversibly delete projects; 'Clean up empty projects' confirms removal of data

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

POLICY

How to control cleanup_empty_projects

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

policy.json

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

cleanup_empty_projects 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 DevMind MCP — 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 DevMind MCP tools

Destructive delete_context Delete a recorded context by ID. Destructive manage_session Manage development sessions: end, delete, or end and delete. Write create_session Create a new development session for a project (or reuse existing active session) Write record_context Record development context to memory. Call IMMEDIATELY after file changes. WHEN TO USE: - Write update_context Update existing memory context to avoid duplicate records. WHEN TO USE: - User explicitly Read get_context Retrieve full details of specific contexts by their IDs or find related contexts. WHEN TO Read get_current_session Get the current active session for a project Read get_memory_status Get memory system status: monitoring state, context count, cache stats.

All 13 DevMind MCP 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 DevMind MCP → 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_empty_projects

What does the cleanup_empty_projects tool do? +

Clean up empty projects (projects with no memory contexts). Returns list of empty projects and optionally deletes them. It is categorised as a Destructive tool in the DevMind MCP 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_empty_projects? +

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

What risk level is cleanup_empty_projects? +

cleanup_empty_projects 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_empty_projects? +

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

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

cleanup_empty_projects is provided by the DevMind MCP server (jochenyang/devmind-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every DevMind MCP tool call.

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

CHECK YOUR STACK →