Create a NEW task in OmniFocus. Use this ONLY when the task does not already exist. If a matching task already exists (e.g. an item already in the Inbox, or one referenced earlier in the conversation) and the goal is to file/place/move it into a project or the inbox, do NOT create a duplicate her...
AI agents use add_omnifocus_task to create or update resources in OmniFocus-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniFocus-MCP environment.
This tool creates new tasks in OmniFocus, which modifies the user's task database. While the creation is reversible (tasks can be deleted), it represents a Write operation that introduces new data into the system.
From the tool's definition Create a NEW task in OmniFocus
Documented attack patterns abuse exactly the kind of access add_omnifocus_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_omnifocus_task:
{
"version": "1",
"default": "deny",
"tools": {
"add_omnifocus_task": {
"limits": [
{
"counter": "add_omnifocus_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_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.
Free to start. No card required.
Create a NEW task in OmniFocus. Use this ONLY when the task does not already exist. If a matching task already exists (e.g. an item already in the Inbox, or one referenced earlier in the conversation) and the goal is to file/place/move it into a project or the inbox, do NOT create a duplicate here — use edit_item with newProjectName to MOVE the existing task instead. When unsure whether a matching task already exists, search with query_omnifocus first and prefer moving over creating. It is categorised as a Write tool in the OmniFocus-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OmniFocus- MCP server in PolicyLayer and add a rule for add_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 OmniFocus-MCP. Nothing to install.
add_omnifocus_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_omnifocus_task is provided by the OmniFocus- MCP server (themotionmachine/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 OmniFocus-MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 OmniFocus-MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.