Medium Risk

complete_task

Mark a task as completed

Part of the Omnifocus MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use complete_task to create or modify resources in Omnifocus. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call complete_task repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Omnifocus.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

omnifocus.yaml
tools:
  complete_task:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Omnifocus policy for all 51 tools.

Tool Name complete_task
Category Write
Risk Level Medium

View all 51 tools →

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

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the complete_task tool do? +

Mark a task as completed. It is categorised as a Write tool in the Omnifocus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_task? +

Add a rule in your Intercept YAML policy under the tools section for complete_task. 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 complete_task? +

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

Can I rate-limit complete_task? +

Yes. Add a rate_limit block to the complete_task 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 complete_task completely? +

Set action: deny in the Intercept policy for complete_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_task? +

complete_task 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.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.