delete_tag

// WHEN AI AGENTS USE THIS TOOL

AI agents may call delete_tag to permanently remove or destroy resources in Omnifocus. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON DELETE_TAG

Without a policy, an AI agent could call delete_tag in a loop, permanently destroying resources in Omnifocus. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

omnifocus.yaml

tools:
  delete_tag:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Omnifocus policy for all 51 tools.

// DETAILS

Tool Name delete_tag

Category Destructive

MCP Server Omnifocus MCP Server

Risk Level Critical

// MORE OMNIFOCUS TOOLS

Destructive batch_delete_tasks Destructive delete_folder Destructive delete_project Destructive delete_task Destructive drop_project Destructive drop_task Destructive remove_task_notification Destructive sync_database

View all 51 tools →

// WHAT CAN GO WRONG

Agents calling destructive-class tools like delete_tag have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER DESTRUCTIVE TOOLS ACROSS MCP SERVERS

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

AbraFlexi contact_delete AbraFlexi evidence_delete AbraFlexi invoice_issued_delete AbraFlexi product_delete ACR — Agent Composition Records acknowledge_threat AdButler campaign_bulk_delete_catalog_ad_items

// IN CONTEXT OF CRITICAL RISK

delete_tag is one of the critical-risk operations in Omnifocus. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the delete_tag tool do? +

Permanently delete a tag from OmniFocus. It is categorised as a Destructive tool in the Omnifocus MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_tag? +

Add a rule in your Intercept YAML policy under the tools section for delete_tag. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Omnifocus MCP server.

What risk level is delete_tag? +

delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_tag? +

Yes. Add a rate_limit block to the delete_tag rule in your Intercept 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.

How do I block delete_tag completely? +

Set action: deny in the Intercept policy for delete_tag. 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.

What MCP server provides delete_tag? +

delete_tag is provided by the Omnifocus MCP server (omnifocus-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.