edit_item · Codex Omnifocus MCP: Risk & Policy

WHAT IT DOES

What edit_item does on Codex Omnifocus

AI agents use edit_item to create or update resources in Codex Omnifocus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codex Omnifocus environment.

WHY IT NEEDS A POLICY

Why edit_item needs a policy

The tool modifies existing data (tasks and projects) through edits and moves, which is a core Write operation. While edits are reversible and don't permanently destroy data, they can affect task state, deadlines, and project hierarchy. Severity is medium because unintended modifications could disrupt task management workflow, but changes can generally be undone.

From the tool's definition Tool description states 'Edit an existing task or project in OmniFocus' and 'supports moving tasks', which are reversible modifications to task/project metadata and structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edit_item Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "edit_item": {
      "limits": [
        {
          "counter": "edit_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Codex Omnifocus, so you can run agents against it safely.

FAQ

Questions about edit_item

What does the edit_item tool do? +

Edit an existing task or project in OmniFocus. Also supports moving tasks via project, parent task, or inbox move fields. It is categorised as a Write tool in the Codex Omnifocus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on edit_item? +

Register the Codex 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 Codex Omnifocus. Nothing to install.

What risk level is edit_item? +

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

Can I rate-limit edit_item? +

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.

How do I block edit_item completely? +

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.

What MCP server provides edit_item? +

edit_item is provided by the Codex Omnifocus MCP server (phd-peter/codex-omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.