Remove a label from a task.
AI agents call vikunja_remove_label_from_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.
Removing a label from a task deletes the association between the label and the task. While the label itself is not deleted, the relationship is removed and would need to be manually re-added. This falls under Destructive as it is an irreversible removal action, similar to other delete operations on the server (vikunja_delete_project, vikunja_delete_task).
From the tool's definition 'Remove a label from a task' — removes an association between a label and a task, which is an irreversible deletion of that relationship without an explicit undo mechanism
Attacks that exploit this kind of access
Remove a label from a task. 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_remove_label_from_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_remove_label_from_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_remove_label_from_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_remove_label_from_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_remove_label_from_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 →