Delete a task by ID.
AI agents call vikunja_delete_task to permanently remove resources in Vikunja — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a task from the Vikunja task management system. Deletion is inherently destructive and irreversible. While the blast radius is limited to a single task (not organizational data like projects), the operation cannot be undone, warranting the Destructive category and high severity. An AI agent could accidentally delete important tasks if given incorrect IDs or if prompt injection occurs.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a task by ID.' This is an irreversible deletion operation that cannot be undone.
Attacks that exploit this kind of access
Delete a task by ID. It is categorised as a Destructive tool in the Vikunja MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vikunja MCP server in PolicyLayer and add a rule for vikunja_delete_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. Nothing to install.
vikunja_delete_task 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_delete_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.
Set action: deny in the PolicyLayer policy for vikunja_delete_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.
vikunja_delete_task is provided by the Vikunja MCP server (shichao402/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →