This record as markdown: /tools/0xk3vin-vikunja-mcp/task-assignees-add.md
What task_assignees_add does on Vikunja
AI agents use task_assignees_add 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.
Why task_assignees_add is rated Medium
This tool modifies task metadata by adding an assignee, which is a write operation. It has moderate severity because incorrect assignment could disrupt workflow (e.g., assigning critical tasks to wrong users), but the effect is limited to a single task relationship and is easily reversible. The blast radius is constrained to task assignment logic rather than data destruction or system-wide impact.
From the tool's definition The tool name 'task_assignees_add' and description 'Add an assignee to a task' indicate a modification operation that creates a relationship between a user and a task without destroying data.
Attacks that exploit this kind of access
The rule that runs task_assignees_add 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_add, this is the rule to start with:
task_assignees_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every task_assignees_add call is checked against it from then on.
Questions about task_assignees_add
Add an assignee to 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 task_assignees_add: 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.
task_assignees_add 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 task_assignees_add 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 task_assignees_add. 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.
task_assignees_add 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.
More on Vikunja, and thousands of servers like it.
This server
Across the catalogue