Move an existing task to a project, parent task, or inbox
AI agents use move_task to create or update resources in OmniFocus MCP Enhanced — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniFocus MCP Enhanced environment.
Moving a task changes its metadata (parent project or task reference) but does not create, delete, or irreversibly destroy data. This is a Write operation because it modifies task state reversibly. Severity is medium because misuse could reorganize a user's task structure in disruptive ways (e.g., moving critical tasks to hidden projects), but the effect is easily undone by moving them back.
From the tool's definition Tool description states 'Move an existing task to a project, parent task, or inbox', which modifies the structural organization of tasks without deleting data. The operation is reversible—tasks can be moved back to their original location.
Documented attack patterns abuse exactly the kind of access move_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniFocus MCP Enhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for move_task:
{
"version": "1",
"default": "deny",
"tools": {
"move_task": {
"limits": [
{
"counter": "move_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_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 an existing task to a project, parent task, or inbox. It is categorised as a Write tool in the OmniFocus MCP Enhanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OmniFocus MCP Enhanced MCP server in PolicyLayer and add a rule for move_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 Enhanced. Nothing to install.
move_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 move_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 move_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.
move_task is provided by the OmniFocus MCP Enhanced MCP server (jqlts1/omnifocus-mcp-enhanced). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniFocus MCP Enhanced, 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.
18 OmniFocus MCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.