Edit an existing task or project in OmniFocus. This is also how you MOVE/reassign an existing task: set newProjectName to a project name/path to move it into that project, or to \
AI agents use edit_item 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 modifies existing tasks and projects in OmniFocus by editing their properties and moving them between projects. These changes are reversible (can be edited again), making this a Write operation rather than Destructive. The blast radius is medium because incorrect edits could corrupt task organization or lose important task details, but changes can be undone in OmniFocus.
From the tool's definition Edit an existing task or project in OmniFocus. This is also how you MOVE/reassign an existing task: set newProjectName to a project name/path to move it into that project
Documented attack patterns abuse exactly the kind of access edit_item 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 edit_item:
{
"version": "1",
"default": "deny",
"tools": {
"edit_item": {
"limits": [
{
"counter": "edit_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}edit_item 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.
Edit an existing task or project in OmniFocus. This is also how you MOVE/reassign an existing task: set newProjectName to a project name/path to move it into that project, or to \. 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 edit_item: 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.
edit_item 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 edit_item 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 edit_item. 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.
edit_item 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.