Remove multiple tasks or projects from OmniFocus in a single operation. Prefer IDs for destructive batch operations.
AI agents call batch_remove_items to permanently remove resources in Codex Omnifocus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes multiple items (tasks or projects) from the user's OmniFocus database in a batch operation. Removal/deletion cannot be undone and represents a destructive action affecting data persistence. The batch nature and potential to affect many items simultaneously increases the blast radius if an AI agent misuses this tool. This is the most severe applicable category.
From the tool's definition Tool description explicitly states "Remove multiple tasks or projects from OmniFocus in a single operation" and is categorized as a destructive batch operation.
Attacks that exploit this kind of access
Remove multiple tasks or projects from OmniFocus in a single operation. Prefer IDs for destructive batch operations. It is categorised as a Destructive tool in the Codex Omnifocus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Codex 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 Codex Omnifocus. 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 Codex Omnifocus MCP server (phd-peter/codex-omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →