AI agents use add_omnifocus_task to create or update resources in OmniFocus MCP Enhanced — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniFocus MCP Enhanced environment.
This tool creates new task entries in OmniFocus. It modifies the application state by adding data, which is characteristic of Write category operations. The impact is reversible (tasks can be deleted), and there are no destructive, financial, or code execution implications.
From the tool's definition Tool name 'add_omnifocus_task' and description 'Add a new task to OmniFocus' indicate creation of new data in the OmniFocus database. This is a reversible write operation.
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 Enhanced, 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.
Add a new task to OmniFocus. It is categorised as a Write tool in the OmniFocus MCP Enhanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OmniFocus MCP Enhanced 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 Enhanced. 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 Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Enhanced, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.