duplicate_project · OmniFocus MCP Server MCP: Risk & Policy

WHAT IT DOES

What duplicate_project does on OmniFocus MCP Server

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

The tool creates a copy of an existing project with all its tasks, which is a Write operation (data creation). It is not a Read operation because it modifies system state by adding new entities. It is not Destructive because duplication does not remove or irreversibly alter existing data. It is not Execute or Financial.

From the tool's definition Tool name 'duplicate_project' and description states 'Create a copy of a project including all its tasks.' This is a creation operation that adds new data to the system reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

duplicate_project Rate-limited

duplicate_project 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": {
    "duplicate_project": {
      "limits": [
        {
          "counter": "duplicate_project_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 duplicate_project

What does the duplicate_project tool do? +

Create a copy of a project including all its tasks. Useful for templates and recurring workflows. Supports date shifting and hierarchy preservation. 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 duplicate_project? +

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

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

Can I rate-limit duplicate_project? +

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

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

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