Critical Risk →

batch_delete_tasks

Delete multiple tasks at once. More efficient than deleting one by one.

Bulk/mass operation — affects multiple targets

Part of the Omnifocus MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

omnifocus-mcp-server Destructive

AI agents may call batch_delete_tasks to permanently remove or destroy resources in Omnifocus. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call batch_delete_tasks in a loop, permanently destroying resources in Omnifocus. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

omnifocus.yaml
tools:
  batch_delete_tasks:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Omnifocus policy for all 51 tools.

Tool Name batch_delete_tasks
Category Destructive
Risk Level Critical

View all 51 tools →

Agents calling destructive-class tools like batch_delete_tasks have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

batch_delete_tasks is one of the critical-risk operations in Omnifocus. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the batch_delete_tasks tool do? +

Delete multiple tasks at once. More efficient than deleting one by one.. It is categorised as a Destructive tool in the Omnifocus 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 batch_delete_tasks? +

Add a rule in your Intercept YAML policy under the tools section for batch_delete_tasks. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Omnifocus MCP server.

What risk level is batch_delete_tasks? +

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

Yes. Add a rate_limit block to the batch_delete_tasks rule in your Intercept 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 batch_delete_tasks completely? +

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

batch_delete_tasks is provided by the Omnifocus MCP server (omnifocus-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.