Move a task before or after another task within the same project/level.
AI agents use reorder_task 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.
Reordering tasks changes their position within a project hierarchy but does not create, delete, or execute anything. The operation is fully reversible—tasks can be moved back to their original positions. This qualifies as a Write operation (modification of existing data) with low severity since the blast radius is limited to task organization without affecting task content, access, or external systems.
From the tool's definition Tool description states 'Move a task before or after another task' which modifies the order/position of existing tasks. This is a reversible structural change to task metadata (sequencing), not data deletion or code execution.
Documented attack patterns abuse exactly the kind of access reorder_task 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_task:
{
"version": "1",
"default": "deny",
"tools": {
"reorder_task": {
"limits": [
{
"counter": "reorder_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reorder_task 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 task before or after another task within the same project/level. 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_task: 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_task 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_task 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_task. 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_task 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.