batch_remove_items

PREFERRED: Remove multiple tasks/projects in ONE call. 9x faster than individual remove_item calls. Always use this for 2+ items.

Server OmniFocus MCP Server mojenmojen/of-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What batch_remove_items does on OmniFocus MCP Server

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

Why batch_remove_items needs a policy

Removal/deletion operations cannot be undone and result in permanent data loss. The batch capability makes this particularly severe—a single misdirected call can destroy many items at once. This is more destructive than Write (reversible modifications) and falls clearly into the Destructive category despite the server offering comprehensive CRUD operations elsewhere.

From the tool's definition Tool name 'batch_remove_items' with description stating 'Remove multiple tasks/projects in ONE call' indicates irreversible deletion of data. The emphasis on batch removal of '2+ items' amplifies the blast radius.

Risk signalsBulk/mass operation — affects multiple targets

Questions about batch_remove_items

What does the batch_remove_items tool do? +

PREFERRED: Remove multiple tasks/projects in ONE call. 9x faster than individual remove_item calls. Always use this for 2+ items. 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 batch_remove_items? +

Register the OmniFocus MCP Server 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 Server. 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 Server MCP server (mojenmojen/of-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.