Move a project before or after another project within the same folder.
AI agents use reorder_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.
This tool modifies data (project order) but does so reversibly; reordering can be undone by reordering again. It does not delete, execute arbitrary commands, or create financial obligations. It falls under Write rather than Execute because the effect is a straightforward state change dependent only on which projects exist, not on dynamic code execution.
From the tool's definition Tool description states it 'Move[s] a project before or after another project' — a reversible modification of project ordering/hierarchy. The action creates or modifies the state of the OmniFocus application by reordering projects.
Documented attack patterns abuse exactly the kind of access reorder_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reorder_project:
{
"version": "1",
"default": "deny",
"tools": {
"reorder_project": {
"limits": [
{
"counter": "reorder_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reorder_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.
Free to start. No card required.
Move a project before or after another project within the same folder. 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.
Register the OmniFocus MCP Server MCP server in PolicyLayer and add a rule for reorder_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.
reorder_project 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 reorder_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.
Set action: deny in the PolicyLayer policy for reorder_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.
reorder_project is provided by the OmniFocus MCP Server MCP server (s-morgan-jeffries/omnifocus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Server, 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.
21 OmniFocus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.