vikunja_tasks
Manage tasks with comprehensive operations (create, update, delete, list, assign, attach files, comment, bulk operations)
This record as markdown: /tools/democratize-technology-vikunja-mcp/vikunja-tasks.md
What vikunja_tasks does on Vikunja MCP Server
AI agents call vikunja_tasks 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_tasks is rated Critical
While the tool includes reversible operations (create, update, list, assign, attach, comment), the explicit mention of delete—especially paired with bulk operations—establishes it as capable of irreversibly removing data at scale. Delete operations are irreversible and cannot be undone, placing this in the Destructive category.
From the tool's definition Tool description explicitly lists "delete" and "bulk operations" alongside create, update, list, assign, attach, and comment capabilities. The combination of delete with bulk operations indicates capacity for irreversible, large-scale data removal.
Attacks that exploit this kind of access
The rule that runs vikunja_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vikunja_tasks, this is the rule to start with:
vikunja_tasks is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja MCP Server, apply this rule, and every vikunja_tasks call is checked against it from then on.
Questions about vikunja_tasks
Manage tasks with comprehensive operations (create, update, delete, list, assign, attach files, comment, bulk operations). 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.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for vikunja_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 MCP Server. Nothing to install.
vikunja_tasks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the vikunja_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.
Set action: deny in the PolicyLayer policy for vikunja_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.
vikunja_tasks 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.
Across the catalogue