move_task_to_bucket · Vikunja MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_task_to_bucket does on Vikunja MCP Server

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

WHY IT NEEDS A POLICY

Why move_task_to_bucket needs a policy

This tool performs a state modification (moving a task to a different bucket) which is characteristic of Write operations. While the action is reversible and the task remains intact, it does alter the organizational structure and status representation of a task in the kanban system.

From the tool's definition The tool 'move_task_to_bucket' modifies the state of a task by relocating it within a kanban board's bucket structure. This is a reversible operation that changes task metadata/organization without creating or deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_task_to_bucket Rate-limited

move_task_to_bucket 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_task_to_bucket": {
      "limits": [
        {
          "counter": "move_task_to_bucket_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 Vikunja MCP Server, so you can run agents against it safely.

FAQ

Questions about move_task_to_bucket

What does the move_task_to_bucket tool do? +

Move a task to a different kanban bucket. It is categorised as a Write tool in the Vikunja 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 move_task_to_bucket? +

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

What risk level is move_task_to_bucket? +

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

Can I rate-limit move_task_to_bucket? +

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

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

move_task_to_bucket is provided by the Vikunja MCP Server MCP server (wosh-i/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.