batch_move_tasks · Todoist MCP Server MCP: Risk & Policy

WHAT IT DOES

What batch_move_tasks does on Todoist MCP Server

AI agents use batch_move_tasks 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.

WHY IT NEEDS A POLICY

Why batch_move_tasks needs a policy

Moving tasks between projects/sections is a reversible modification operation—tasks remain intact but change state/location. This is Write rather than Destructive (no deletion), Read (modifies state), or Execute (no code execution). The batch operation affects multiple items, raising severity to medium despite being reversible, as an agent could reorganize significant task structures unintentionally.

From the tool's definition Tool name 'batch_move_tasks' indicates modification of task positions/organization. Sibling tools on the server include 'batch_complete_tasks', 'batch_update_tasks', 'add_task', 'delete_comment', and 'delete_label', establishing this as a task management…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_move_tasks Rate-limited

batch_move_tasks 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": {
    "batch_move_tasks": {
      "limits": [
        {
          "counter": "batch_move_tasks_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 Todoist MCP Server, so you can run agents against it safely.

FAQ

Questions about batch_move_tasks

What does the batch_move_tasks tool do? +

batch_move_tasks. 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 batch_move_tasks? +

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

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

Can I rate-limit batch_move_tasks? +

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

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

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