ticktick_move_task · Ticktick MCP: Risk & Policy

WHAT IT DOES

What ticktick_move_task does on Ticktick

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

WHY IT NEEDS A POLICY

Why ticktick_move_task needs a policy

Moving a task between projects modifies data state reversibly: the task is created in the target project and marked complete in the source. This is a write operation (state change via create+complete) rather than destructive (no permanent deletion), execute (no code execution or external side effects), or read (has side effects).

From the tool's definition Tool description states it 'move[s] a task from one project/list to another. This creates the task in the target project and completes it in the source.' The operation modifies task state (moves and completes) but is reversible—tasks can be moved again or…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticktick_move_task Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ticktick_move_task": {
      "limits": [
        {
          "counter": "ticktick_move_task_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 Ticktick, so you can run agents against it safely.

FAQ

Questions about ticktick_move_task

What does the ticktick_move_task tool do? +

Use this to move a task from one project/list to another. This creates the task in the target project and completes it in the source. Required: sourceProjectId, taskId, targetProjectId. It is categorised as a Write tool in the Ticktick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ticktick_move_task? +

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

What risk level is ticktick_move_task? +

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

Can I rate-limit ticktick_move_task? +

Yes. Add a rate_limit block to the ticktick_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.

How do I block ticktick_move_task completely? +

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

What MCP server provides ticktick_move_task? +

ticktick_move_task is provided by the Ticktick MCP server (produckteavity/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.