AI agents use remove_label_from_task to create or update resources in Vikunja — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vikunja environment.
Removing a label from a task modifies the task's metadata but is reversible (the label can be re-added), so it falls under Write rather than Destructive. The blast radius is low as it only affects label associations on a single task.
From the tool's definition Remove a label from a task
Attacks that exploit this kind of access
Remove a label from a task. It is categorised as a Write tool in the Vikunja MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vikunja MCP server in PolicyLayer and add a rule for 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.
remove_label_from_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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 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.
remove_label_from_task is provided by the Vikunja MCP server (ugoi/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 →