batch_mark_reviewed · OmniFocus MCP Server MCP

WHAT IT DOES

What batch_mark_reviewed does on OmniFocus MCP Server

AI agents use batch_mark_reviewed 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_mark_reviewed needs a policy

Batch marking projects as reviewed updates project metadata (next review dates) but does not delete or irreversibly destroy data. The operation is reversible — review dates can be changed again. This is a Write operation (modify data) rather than Execute (triggering external side effects) or Destructive (irreversible deletion).

From the tool's definition Tool description states it 'Mark[s] multiple projects as reviewed in a single operation (advances their next review dates)' — this modifies project state by updating review metadata reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_mark_reviewed Rate-limited

batch_mark_reviewed 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_mark_reviewed": {
      "limits": [
        {
          "counter": "batch_mark_reviewed_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_mark_reviewed

What does the batch_mark_reviewed tool do? +

Mark multiple projects as reviewed in a single operation (advances their next review dates). 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_mark_reviewed? +

Register the OmniFocus MCP Server MCP server in PolicyLayer and add a rule for batch_mark_reviewed: 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_mark_reviewed? +

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

Can I rate-limit batch_mark_reviewed? +

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

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

batch_mark_reviewed 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.