// SCAN REPORT

OmniFocus MCP Server

31 tools. 11 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

11 can modify or destroy data

20 read-only

31 tools total

Community server · catalogue entry verified 29/06/2026

How to control OmniFocus MCP Server ↓

TOOL MAP

What OmniFocus MCP Server exposes to your agents

Read (20) Write / Execute (9) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous OmniFocus MCP Server tools

Destructive · High batch_remove_items Removal/deletion operations cannot be undone and result in permanent data loss. Destructive · High remove_item This tool permanently deletes tasks or projects from OmniFocus without reversibility. Write · Medium batch_add_items This tool creates or modifies data reversibly by adding multiple tasks and projects to OmniFocus. Write · Medium batch_edit_items This tool modifies (creates or updates) task and project data reversibly within OmniFocus.

11 of OmniFocus MCP Server's 31 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control OmniFocus MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "batch_remove_items": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_folder": {
    "limits": [
      {
        "counter": "add_folder_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "batch_filter_tasks": {
    "limits": [
      {
        "counter": "batch_filter_tasks_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register OmniFocus MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON OMNIFOCUS →

Instant setup, no code required.

FULL CATALOGUE

All 31 OmniFocus MCP Server tools

DESTRUCTIVE 2 tools

Destructive batch_remove_items PREFERRED: Remove multiple tasks/projects in ONE call. 9x faster than individual remove_item calls. Always use Destructive remove_item Remove a SINGLE task or project from OmniFocus. For removing 2+ items, use batch_remove_items instead (9x fast

WRITE 9 tools

Write add_folder Add a new folder to OmniFocus Write add_omnifocus_task Add a SINGLE task to OmniFocus. IMPORTANT: For adding 2+ tasks, use batch_add_items instead (9x faster, single Write add_project Add a SINGLE project to OmniFocus. For adding multiple projects, use batch_add_items instead. Write batch_add_items PREFERRED: Add multiple tasks/projects in ONE call. 9x faster than individual add_omnifocus_task calls. Always Write batch_edit_items PREFERRED: Edit multiple tasks/projects in ONE call. 12x faster than individual edit_item calls. Always use th Write batch_mark_reviewed Mark multiple projects as reviewed in a single operation (advances their next review dates) Write duplicate_project Create a copy of a project including all its tasks. Useful for templates and recurring workflows. Supports dat Write edit_item Edit a SINGLE task or project in OmniFocus. For editing 2+ items, use batch_edit_items instead (12x faster). Write edit_tag Edit a tag

READ 20 tools

Read batch_filter_tasks PREFERRED: Filter tasks across multiple projects in ONE call. Always use this instead of multiple filter_tasks Read diagnose_connection Check OmniFocus connectivity, permissions, and server status. Run this first if experiencing issues. Read filter_tasks Advanced task filtering for ONE project. For filtering across 2+ projects, use batch_filter_tasks instead (sin Read get_completion_stats Get task completion counts grouped by project, tag, or folder for a date range. Returns sorted list with count Read get_custom_perspective_tasks Get tasks from a specific OmniFocus custom perspective by name. Use this when user refers to perspective names Read get_flagged_tasks Get flagged tasks from OmniFocus with optional project filtering Read get_folder_by_id Get information about a specific folder by ID or name Read get_forecast_tasks Get tasks from OmniFocus forecast perspective (due/deferred tasks in date range) Read get_inbox_tasks Get tasks from OmniFocus inbox perspective Read get_project_by_id Get information about a specific project by ID or name Read get_projects_for_review Get projects that are due for review (next review date is in the past or today) Read get_server_version Get OmniFocus MCP server version and build information Read get_system_health Get all OmniFocus health metrics in a single call. Returns counts for inbox, projects (by status), tasks (by s Read get_task_by_id Get information about a specific task by ID or name Read get_tasks_by_tag Get tasks filtered by OmniFocus tags (labels like @home, @work, @urgent). Use this for tag-based filtering, NO Read get_today_completed_tasks Get tasks completed today - view today Read list_custom_perspectives List all custom perspectives defined in OmniFocus Read list_projects List projects with optional folder and status filtering - the targeted way to discover projects and their IDs Read search_tasks Full-text search across task names and notes. Simpler than filter_tasks for finding tasks by text. Supports ma

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about OmniFocus MCP Server

Can an AI agent delete data through the OmniFocus MCP Server MCP server? +

Yes. The OmniFocus MCP Server server exposes 2 destructive tools including batch_remove_items, remove_item. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through OmniFocus MCP Server? +

The OmniFocus MCP Server server has 9 write tools including add_folder, add_omnifocus_task, add_project. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach OmniFocus MCP Server.

How many tools does the OmniFocus MCP Server MCP server expose? +

31 tools across 4 categories: Destructive, Execute, Read, Write. 20 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on OmniFocus MCP Server? +

Register the OmniFocus MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every OmniFocus MCP Server tool call.

Deterministic rules across all 31 OmniFocus MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON OMNIFOCUS →

Instant setup, no code required.

31 OmniFocus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.