vikunja_add_label_to_task · Vikunja MCP: Risk & Policy

WHAT IT DOES

What vikunja_add_label_to_task does on Vikunja

AI agents use vikunja_add_label_to_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_add_label_to_task needs a policy

This tool creates a new relationship between a task and an existing label. It modifies task state (the label assignment) but does not create, delete, or destroy data—the change can be undone by removing the label. This is a typical Write operation: it updates data reversibly. Severity is medium because mislabeling tasks could cause workflow confusion and incorrect task categorization, but the impact is recoverable.

From the tool's definition Tool description states "Attach an existing label to a task" — this modifies task metadata by adding a label association, which is a reversible data mutation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vikunja_add_label_to_task Rate-limited

vikunja_add_label_to_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_add_label_to_task": {
      "limits": [
        {
          "counter": "vikunja_add_label_to_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_add_label_to_task

What does the vikunja_add_label_to_task tool do? +

Attach an existing label to a task. 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_add_label_to_task? +

Register the Vikunja MCP server in PolicyLayer and add a rule for vikunja_add_label_to_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_add_label_to_task? +

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

Can I rate-limit vikunja_add_label_to_task? +

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

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

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