Remove multiple tasks or projects from OmniFocus in a single operation
AI agents call batch_remove_items to permanently remove resources in OmniFocus-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes multiple items at once without the ability to undo. The batch nature amplifies risk since a single call can destroy many tasks/projects simultaneously. While not financial, the irreversible data loss qualifies it as Destructive (more severe than Write). High severity due to potential bulk data loss; high confidence due to explicit removal language in name and description.
From the tool's definition Tool name 'batch_remove_items' and description states it will 'Remove multiple tasks or projects from OmniFocus in a single operation' - removal is irreversible deletion.
Documented attack patterns abuse exactly the kind of access batch_remove_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_remove_items:
{
"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.
Free to start. No card required.
Remove multiple tasks or projects from OmniFocus in a single operation. It is categorised as a Destructive tool in the OmniFocus-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OmniFocus- 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. Nothing to install.
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.
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.
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.
batch_remove_items is provided by the OmniFocus- MCP server (themotionmachine/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 OmniFocus-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 OmniFocus-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.