vikunja_update_task · Vikunja MCP: Risk & Policy

WHAT IT DOES

What vikunja_update_task does on Vikunja

AI agents use vikunja_update_task 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 IT NEEDS A POLICY

Why vikunja_update_task needs a policy

This tool creates or modifies data reversibly by updating task fields in a task management system. While updates are not destructive (data is not deleted), they do alter state and could impact workflows, deadlines, or task assignments if misused by an AI agent. Classified as Write rather than Read (retrieval only) or Execute (arbitrary code execution).

From the tool's definition Tool name 'vikunja_update_task' and description explicitly states it performs updates with 'PATCH-style semantics' to modify existing tasks. The description confirms 'the fields you pass are changed' indicating reversible modification of data.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vikunja_update_task Rate-limited

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

FAQ

Questions about vikunja_update_task

What does the vikunja_update_task tool do? +

Update an existing task with PATCH-style semantics. By default only the fields you pass are changed; every other field keeps its current value (the MCP server reads the task first and merges your input on top). Set. It is categorised as a Write tool in the Vikunja MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vikunja_update_task? +

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

What risk level is vikunja_update_task? +

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

Can I rate-limit vikunja_update_task? +

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

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

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