AI agents use edit_item 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 modifies existing tasks or projects in OmniFocus, which constitutes a Write operation. It is not Destructive because edits are typically reversible (can be undone or re-edited). The severity is medium because an AI agent could inadvertently modify important tasks, affecting user productivity, though changes are not permanent data loss.
From the tool's definition Tool name 'edit_item' combined with description 'Edit a task or project in OmniFocus' clearly indicates modification of existing data. The verb 'edit' is a reversible write operation.
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 Enhanced, 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 a task or project in 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 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 Enhanced. 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 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.