This record as markdown: /tools/kh0pper-crow/crow-vikunja-delete-task.md
What crow_vikunja_delete_task does on Crow
AI agents call crow_vikunja_delete_task to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why crow_vikunja_delete_task is rated Critical
This tool permanently deletes tasks without the ability to undo the action. Deletion of project management data is irreversible and represents data loss. An AI agent misusing this tool could delete critical project tasks, causing loss of project information and work tracking. This is more severe than Write or Execute actions because the effects cannot be recovered.
From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a task from Vikunja (irreversible)' — the word 'irreversible' confirms the destructive nature of this operation.
Attacks that exploit this kind of access
The rule that runs crow_vikunja_delete_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_vikunja_delete_task, this is the rule to start with:
crow_vikunja_delete_task 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 Crow, apply this rule, and every crow_vikunja_delete_task call is checked against it from then on.
Questions about crow_vikunja_delete_task
Delete a task from Vikunja (irreversible). It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for crow_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 Crow. Nothing to install.
crow_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 crow_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 crow_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.
crow_vikunja_delete_task is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue