batch_edit_items · OmniFocus MCP Server MCP: Risk & Policy

WHAT IT DOES

What batch_edit_items does on OmniFocus MCP Server

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

WHY IT NEEDS A POLICY

Why batch_edit_items needs a policy

This tool modifies (creates or updates) task and project data reversibly within OmniFocus. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial). The batch capability increases the blast radius slightly by allowing multiple items to be modified in a single call, potentially affecting workflow state at scale, warranting medium severity.

From the tool's definition Tool name 'batch_edit_items' and description 'Edit multiple tasks/projects in ONE call' indicate modification of data. The term 'Edit' combined with support for batch operations on tasks/projects confirms data mutation without deletion.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_edit_items Rate-limited

batch_edit_items 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": {
    "batch_edit_items": {
      "limits": [
        {
          "counter": "batch_edit_items_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 OmniFocus MCP Server, so you can run agents against it safely.

FAQ

Questions about batch_edit_items

What does the batch_edit_items tool do? +

PREFERRED: Edit multiple tasks/projects in ONE call. 12x faster than individual edit_item calls. Always use this for 2+ items. It is categorised as a Write tool in the OmniFocus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_edit_items? +

Register the OmniFocus MCP Server MCP server in PolicyLayer and add a rule for batch_edit_items: 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 Server. Nothing to install.

What risk level is batch_edit_items? +

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

Can I rate-limit batch_edit_items? +

Yes. Add a rate_limit block to the batch_edit_items 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 batch_edit_items completely? +

Set action: deny in the PolicyLayer policy for batch_edit_items. 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 batch_edit_items? +

batch_edit_items is provided by the OmniFocus MCP Server MCP server (mojenmojen/of-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.