Drop a task in OmniFocus.
AI agents call drop_task to permanently remove resources in MCP OmniFocus — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'drop_task' tool performs an irreversible deletion operation on task data in OmniFocus. Even though the description is minimal, the use of 'drop' as a verb combined with the task management domain strongly indicates permanent removal rather than a reversible modification. This irreversibility and data loss potential makes it Destructive rather than Write.
From the tool's definition Tool named 'drop_task' with description 'Drop a task in OmniFocus.' The verb 'drop' in task management contexts typically means to permanently delete or discard a task, which is an irreversible action that cannot be undone.
Attacks that exploit this kind of access
Drop a task in OmniFocus. It is categorised as a Destructive tool in the MCP OmniFocus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP OmniFocus MCP server in PolicyLayer and add a rule for drop_task: 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 MCP OmniFocus. Nothing to install.
drop_task 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 drop_task 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 drop_task. 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.
drop_task is provided by the MCP OmniFocus MCP server (someposer/mcp-omnifocus). 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 →