move_tasks · Tick MCP: Risk & Policy

WHAT IT DOES

What move_tasks does on Tick

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

WHY IT NEEDS A POLICY

Why move_tasks needs a policy

Moving tasks changes their organizational state but does not create, delete, or execute arbitrary operations. This is a Write-category action: reversible data modification. Severity is medium because bulk task movements could disrupt workflow organization, but effects are recoverable. Confidence is slightly reduced due to empty description, though the tool name and server context provide reasonable inference.

From the tool's definition Tool name 'move_tasks' indicates modification of task state/position. Description is empty, limiting direct evidence, but sibling tools like 'batch_update_tasks', 'batch_delete_tasks', and 'complete_task' establish this server manages TickTick task mutations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_tasks Rate-limited

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

FAQ

Questions about move_tasks

What does the move_tasks tool do? +

move_tasks. It is categorised as a Write tool in the Tick 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? +

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

What risk level is move_tasks? +

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

Can I rate-limit move_tasks? +

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

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

move_tasks is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.