Update multiple tasks at once. Only the fields you specify are changed — other fields are left untouched. Examples: Mark tasks #1, #2, #3 as done: task_ids=[1,2,3], done=true Set all FIIERCE sprint tasks to high priority: task_ids=[...], priority=3
AI agents use bulk_update_tasks to create or update resources in Vikunja MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vikunja MCP Server environment.
This tool modifies data (task properties like done status and priority) in a reversible manner. Updates can be undone by subsequent writes with different values. It does not delete data (not Destructive), execute arbitrary code (not Execute), or involve financial operations (not Financial).
From the tool's definition Tool description states 'Update multiple tasks at once' with selective field modification. Examples show setting task status and priority fields without deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Update multiple tasks at once. Only the fields you specify are changed — other fields are left untouched. Examples: Mark tasks #1, #2, #3 as done: task_ids=[1,2,3], done=true Set all FIIERCE sprint tasks to high priority: task_ids=[...], priority=3. It is categorised as a Write tool in the Vikunja MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for bulk_update_tasks: 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 MCP Server. Nothing to install.
bulk_update_tasks 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 bulk_update_tasks 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 bulk_update_tasks. 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.
bulk_update_tasks is provided by the Vikunja MCP Server MCP server (lindenlion/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 →