create_omnifocus_task

Creates a new task in OmniFocus. Requires confirm=true to execute.

SERVERLocal SOURCElocal-mcp
Medium RISK CLASS
Category Write
Parameters 71 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/create-omnifocus-task.md

What create_omnifocus_task does on Local

AI agents use create_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.

ParameterTypeRequiredDescription
name string Yes
note string
confirm boolean
flagged boolean
project string
due_date string
defer_date string

Parameters from the server's own tool schema.

Why create_omnifocus_task is rated Medium

This tool creates (writes) data to a local task management system. It is reversible—tasks can be deleted—and has no financial impact, no code execution, and no destructive effects. The requirement for confirm=true provides an additional safety measure. Severity is low because misuse would only clutter a local task list with unwanted items, which is easily remedied. Write is the appropriate category.

From the tool's definition Creates a new task in OmniFocus. The action is task creation, which is reversible data modification. The tool name explicitly uses 'create' and the description confirms this creates a new task.

Questions about create_omnifocus_task

What does the create_omnifocus_task tool do? +

Creates a new task in OmniFocus. Requires confirm=true to execute. 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 create_omnifocus_task accept? +

create_omnifocus_task accepts 7 parameters: name, note, confirm, flagged, project, due_date, defer_date. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_omnifocus_task? +

Register the Local MCP server in PolicyLayer and add a rule for create_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 create_omnifocus_task? +

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

Can I rate-limit create_omnifocus_task? +

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

Set action: deny in the PolicyLayer policy for create_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 create_omnifocus_task? +

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

More on Local, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Local's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.