AI agents call remove_item 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.
Removing tasks or projects from OmniFocus is an irreversible action that permanently deletes user data. This cannot be undone through normal operations and represents data loss. While not as critical as financial transactions, the permanent nature of deletion and potential impact on user productivity warrants 'high' severity.
From the tool's definition Tool description states 'Remove a task or project from OmniFocus' which indicates irreversible deletion of data items. The presence of sibling tool 'batch_remove_items' further confirms deletion capability.
Documented attack patterns abuse exactly the kind of access remove_item 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 remove_item:
{
"version": "1",
"default": "deny",
"hide": [
"remove_item"
]
} remove_item 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 a task or project from OmniFocus. 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 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 OmniFocus-MCP. 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 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.