task_move_to_bucket

What task_move_to_bucket does on Vikunja

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

Why task_move_to_bucket is rated Medium

Moving a task to a different bucket modifies the task's state and position in the kanban workflow, but the operation is fully reversible (the task can be moved back). This is characteristic of Write operations rather than Destructive ones. Severity is medium because misuse could disorganize task workflows, but no data is lost and the impact is limited to a single task's organizational placement.

From the tool's definition Tool name 'task_move_to_bucket' and description 'Move a task to a different kanban bucket' indicate modifying task state by relocating it within a kanban board structure. This is a reversible modification operation.

The rule that runs task_move_to_bucket safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For task_move_to_bucket, this is the rule to start with:

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

Questions about task_move_to_bucket