bulk_create_tasks · Vikunja MCP: Risk & Policy

WHAT IT DOES

What bulk_create_tasks does on Vikunja

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

This tool creates new data (tasks) within Vikunja, which is a Write operation. It is reversible via delete_task, so it does not qualify as Destructive. The bulk nature increases the blast radius from a regular create_task, warranting medium severity—an agent could inadvertently flood a project with tasks. Confidence is high given explicit 'create' action in the description.

From the tool's definition Tool name 'bulk_create_tasks' and description 'Create multiple tasks in a project at once' indicate creation of data. The 'bulk' qualifier suggests potential for high volume writes, but the operation is reversible (tasks can be deleted).

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_create_tasks Rate-limited

bulk_create_tasks 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": {
    "bulk_create_tasks": {
      "limits": [
        {
          "counter": "bulk_create_tasks_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 bulk_create_tasks

What does the bulk_create_tasks tool do? +

Create multiple tasks in a project at once. 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 bulk_create_tasks? +

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

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

Can I rate-limit bulk_create_tasks? +

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

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

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