complete_omnifocus_task

Marks an OmniFocus task as complete by task ID or name. Requires confirm=true.

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/complete-omnifocus-task.md

WHAT IT DOES

What complete_omnifocus_task does on Local

AI agents use complete_omnifocus_task to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.

Parameter	Type	Required
`confirm`	boolean	—
`task_id`	string	—
`task_name`	string	—

Parameters from the server's own tool schema.

RISK

Why complete_omnifocus_task is rated Medium

This tool modifies data (task completion status) reversibly—a task can be marked incomplete again. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely read data (Read). The medium severity reflects that bulk misuse could disrupt a user's task management system, but individual task completions are recoverable.

From the tool's definition Tool description states it 'Marks an OmniFocus task as complete', which modifies task state. The 'confirm=true' requirement indicates intentional safeguard against accidental invocation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs complete_omnifocus_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For complete_omnifocus_task, this is the rule to start with:

complete_omnifocus_task Rate-limited

complete_omnifocus_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "complete_omnifocus_task": {
      "limits": [
        {
          "counter": "complete_omnifocus_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every complete_omnifocus_task call is checked against it from then on.

FAQ

Questions about complete_omnifocus_task

What does the complete_omnifocus_task tool do? +

Marks an OmniFocus task as complete by task ID or name. Requires confirm=true. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does complete_omnifocus_task accept? +

complete_omnifocus_task accepts 3 parameters: confirm, task_id, task_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on complete_omnifocus_task? +

Register the Local MCP server in PolicyLayer and add a rule for complete_omnifocus_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 Local. Nothing to install.

What risk level is complete_omnifocus_task? +

complete_omnifocus_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit complete_omnifocus_task? +

Yes. Add a rate_limit block to the complete_omnifocus_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.

How do I block complete_omnifocus_task completely? +

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

What MCP server provides complete_omnifocus_task? +

complete_omnifocus_task is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →reminders_complete on Apple Apps MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →