todoist_task_move · Mcp Todoist MCP: Risk & Policy

WHAT IT DOES

What todoist_task_move does on Mcp Todoist

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

WHY IT NEEDS A POLICY

Why todoist_task_move needs a policy

The tool modifies task metadata (project, section, parent) but does not delete data or trigger irreversible destructive changes. Task moves are reversible operations—tasks can be moved back to their original locations. This is a data modification action (Write category) rather than Read (no retrieval-only), Execute (no code execution), or Destructive (reversible).

From the tool's definition Tool description states it 'Move a task to a different project, section, or under a parent task', which modifies the state and location of a task within the Todoist system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

todoist_task_move Rate-limited

todoist_task_move 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": {
    "todoist_task_move": {
      "limits": [
        {
          "counter": "todoist_task_move_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 Mcp Todoist, so you can run agents against it safely.

FAQ

Questions about todoist_task_move

What does the todoist_task_move tool do? +

Move a task to a different project, section, or under a parent task. Uses Todoist Sync API for reliable movement operations. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todoist_task_move? +

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

What risk level is todoist_task_move? +

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

Can I rate-limit todoist_task_move? +

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

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

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