task_assignees_remove

Remove an assignee from a task

SERVERVikunja SOURCE0xk3vin/vikunja-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xk3vin-vikunja-mcp/task-assignees-remove.md

WHAT IT DOES

What task_assignees_remove does on Vikunja

AI agents call task_assignees_remove 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.

RISK

Why task_assignees_remove is rated Critical

Removing an assignee is an irreversible deletion of a relationship between a user and a task. While the assignee themselves are not deleted, the assignment record is removed and would need to be manually re-added, making it a destructive operation rather than a simple write/update.

From the tool's definition Remove an assignee from a task

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs task_assignees_remove safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For task_assignees_remove, this is the rule to start with:

task_assignees_remove Hidden

task_assignees_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "task_assignees_remove"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every task_assignees_remove call is checked against it from then on.

FAQ

Questions about task_assignees_remove

What does the task_assignees_remove tool do? +

Remove an assignee 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.

How do I enforce a policy on task_assignees_remove? +

Register the Vikunja MCP server in PolicyLayer and add a rule for task_assignees_remove: 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.

What risk level is task_assignees_remove? +

task_assignees_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit task_assignees_remove? +

Yes. Add a rate_limit block to the task_assignees_remove 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.

How do I block task_assignees_remove completely? +

Set action: deny in the PolicyLayer policy for task_assignees_remove. 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.

What MCP server provides task_assignees_remove? +

task_assignees_remove is provided by the Vikunja MCP server (0xk3vin/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vikunja, and thousands of servers like it.

This server

All 31 Vikunja tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →