delete_projects

THE RISK

Critical Risk

Why delete_projects needs a policy

The delete_projects tool irreversibly removes projects and their associated tasks with no undo capability. This meets the definition of Destructive category: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects the broad blast radius—deleting projects affects not just the project itself but all contained tasks, representing significant data loss if misused by an AI…

From the tool's definition Tool description explicitly states 'Permanently delete projects and all their tasks. Cannot be undone.' This is irreversible destruction of data.

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

POLICY

How to control delete_projects

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

policy.json

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

delete_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 OmniFocus 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 OmniFocus MCP Server tools

Destructive delete_tags Delete tags. Tasks lose tag association but are not deleted. Destructive delete_tasks Permanently delete tasks. Cannot be undone. Execute switch_perspective Switch front window to a perspective. Write create_folders Create one or more folders. Write create_projects create_projects Write create_tags Create one or more tags. Write create_tasks create_tasks Write reorder_project Move a project before or after another project within the same folder.

All 21 OmniFocus 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 OmniFocus 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 delete_projects

What does the delete_projects tool do? +

Permanently delete projects and all their tasks. Cannot be undone. It is categorised as a Destructive tool in the OmniFocus 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 delete_projects? +

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

What risk level is delete_projects? +

delete_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 delete_projects? +

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

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

delete_projects is provided by the OmniFocus MCP Server MCP server (s-morgan-jeffries/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OmniFocus MCP Server tool call.

Start from OmniFocus 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 →