Remove a task or project from OmniFocus
AI agents call remove_item to permanently remove resources in OmniFocus MCP Enhanced — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a task or project from a productivity database is irreversible data loss unless the system maintains backups or trash functionality not mentioned in the description. An AI agent given this tool could accidentally delete important tasks or entire projects. This is more severe than Write (reversible modification) and constitutes a Destructive action.
From the tool's definition Tool name and description explicitly state 'Remove a task or project from OmniFocus' with no mention of undo, archiving, or reversibility. The verb 'remove' combined with 'from OmniFocus' indicates deletion rather than modification.
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 Enhanced, 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 Enhanced MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OmniFocus MCP Enhanced 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 Enhanced. 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 Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Enhanced, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.