move_tasks_to_project

ServerTodoist MCP Server
CategoryWrite

WHAT IT DOES

What move_tasks_to_project does on Todoist MCP Server

AI agents use move_tasks_to_project to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.

THE RISK

Medium Risk

Why move_tasks_to_project needs a policy

This tool modifies task properties (project assignment) in a reversible manner. Tasks can be moved back to their original projects or reassigned to different projects. While the action affects task organization, it does not destroy data or execute arbitrary code.

From the tool's definition Tool description states it 'Move multiple tasks to a different project' and 'Returns the updated task objects after successful movement', indicating reversible modification of task metadata (project assignment).

Documented attack patterns abuse exactly the kind of access move_tasks_to_project gives an agent:

POLICY

How to control move_tasks_to_project

PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_tasks_to_project:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_tasks_to_project": {
      "limits": [
        {
          "counter": "move_tasks_to_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Todoist MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Todoist MCP Server tools

Destructive delete_comment Permanently delete a comment by its unique identifier. This action will remove the comment Destructive delete_label PERMANENTLY delete a personal label by its ID. WARNING: This action is IRREVERSIBLE and wi Destructive delete_project Permanently delete a Todoist project by its unique identifier. This action will remove the Destructive delete_section Permanently delete a Todoist section by its unique identifier. This action will remove the Destructive delete_task Permanently delete a Todoist task by its unique identifier. This action will remove the ta Write close_task Mark a Todoist task as completed. This action moves the task to the completed state while Write create_label Create a new personal label with customizable properties including name, color, display or Write create_project Create a new Todoist project with customizable settings. Allows you to set up a project wi

All 32 Todoist MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about move_tasks_to_project

What does the move_tasks_to_project tool do? +

Move multiple tasks to a different project within Todoist. This will move the tasks from their current location to the specified project. Useful for reorganizing tasks when project assignments change or for bulk task management. Returns the updated task objects after successful movement with their new project assignment. It is categorised as a Write tool in the Todoist 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 move_tasks_to_project? +

Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for move_tasks_to_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 Todoist MCP Server. Nothing to install.

What risk level is move_tasks_to_project? +

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

Can I rate-limit move_tasks_to_project? +

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

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

move_tasks_to_project is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Todoist MCP Server tool call.

Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.