add_task_label · Vikunja MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_task_label does on Vikunja MCP Server

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

Adding a label modifies task metadata in a way that can be undone (by removing the label). This is a Write operation rather than Read (it changes state), Execute (it doesn't run code or trigger external logic), Destructive (it's reversible), or Financial (no money involved). The blast radius is minimal since label changes don't affect critical task data or other systems.

From the tool's definition Tool name 'add_task_label' and description 'Add a label to a task' indicate a label is being added to an existing task. This is a reversible modification operation (labels can be removed).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_task_label Rate-limited

add_task_label 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": {
    "add_task_label": {
      "limits": [
        {
          "counter": "add_task_label_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 add_task_label

What does the add_task_label tool do? +

Add a label to a task. 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 add_task_label? +

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

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

Can I rate-limit add_task_label? +

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

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

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