add_label_to_task · Vikunja MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_label_to_task does on Vikunja MCP Server

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

This tool modifies task state by associating a label, which is a typical Write operation (create or modify data reversibly). The action is easily reversible (the label can be removed), and the blast radius of misuse is low—it would only alter task organization metadata. No side effects, code execution, financial impact, or permanent data loss are involved.

From the tool's definition Tool description states 'Attach an existing label to a task' — a reversible modification operation. The name contains 'add', which is a Write action that modifies task metadata without destructive or financial consequences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_label_to_task Rate-limited

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

FAQ

Questions about add_label_to_task

What does the 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 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_label_to_task? +

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

What risk level is add_label_to_task? +

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 add_label_to_task? +

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

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

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