Critical Risk →

batch_remove_items

Remove multiple tasks or projects from OmniFocus in a single operation

How to control batch_remove_items ↓

What batch_remove_items does on OmniFocus MCP Enhanced

AI agents call batch_remove_items to permanently remove resources in OmniFocus MCP Enhanced — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why batch_remove_items needs a policy

Removing tasks or projects from OmniFocus deletes data that cannot be automatically recovered through the tool itself. 'Remove' semantics in task management systems typically mean permanent deletion. The batch operation capability increases severity by enabling large-scale data loss in a single call.

From the tool's definition Tool name 'batch_remove_items' combined with description 'Remove multiple tasks or projects from OmniFocus in a single operation' indicates irreversible deletion.

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

How to control batch_remove_items

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "batch_remove_items"
  ]
}

batch_remove_items disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register OmniFocus MCP Enhanced — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about batch_remove_items

What does the batch_remove_items tool do? +

Remove multiple tasks or projects from OmniFocus in a single operation. It is categorised as a Destructive tool in the OmniFocus MCP Enhanced 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_remove_items? +

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

What risk level is batch_remove_items? +

batch_remove_items 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_remove_items? +

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

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

batch_remove_items is provided by the OmniFocus MCP Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). 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 Enhanced tool call.

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

Free to start. No card required.

18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.