New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

vikunja_task_bulk

Manage bulk task operations: create, update, delete multiple tasks

SERVERVikunja MCP Server SOURCEdemocratize-technology/vikunja-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/democratize-technology-vikunja-mcp/vikunja-task-bulk.md

What vikunja_task_bulk does on Vikunja MCP Server

AI agents call vikunja_task_bulk to permanently remove resources in Vikunja MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why vikunja_task_bulk is rated Critical

While the tool includes create and update capabilities (Write operations), the explicit mention of 'delete multiple tasks' makes this Destructive. Bulk deletion is irreversible and has significant blast radius if misused by an AI agent. Destructive supersedes Write in severity hierarchy.

From the tool's definition Tool description explicitly states 'delete multiple tasks' — a destructive operation that irreversibly removes data. The bulk nature amplifies risk.

Questions about vikunja_task_bulk

What does the vikunja_task_bulk tool do? +

Manage bulk task operations: create, update, delete multiple tasks. It is categorised as a Destructive tool in the Vikunja MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on vikunja_task_bulk? +

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

vikunja_task_bulk is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit vikunja_task_bulk? +

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

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

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

More on Vikunja MCP Server, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vikunja MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.