Remove a task or project from OmniFocus. Prefer ID over name for destructive operations.
AI agents call remove_item 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.
The remove_item tool irreversibly deletes tasks or projects from the user's OmniFocus database. This is a destructive operation that cannot be undone and results in permanent data loss. While severity is not critical because it affects only the user's own task database (not financial or system-wide impact), it is high because task loss can significantly disrupt user workflows.
From the tool's definition Tool description explicitly states "Remove a task or project from OmniFocus" and recommends using ID "for destructive operations", directly acknowledging the destructive nature of the action.
Attacks that exploit this kind of access
Remove a task or project from OmniFocus. Prefer ID over name for destructive 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 remove_item: 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.
remove_item 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 remove_item 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 remove_item. 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.
remove_item 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 →