vikunja_batch_import
Import tasks in bulk from CSV or JSON formats with error handling and dry-run support
This record as markdown: /tools/democratize-technology-vikunja-mcp/vikunja-batch-import.md
What vikunja_batch_import does on Vikunja MCP Server
AI agents use vikunja_batch_import 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.
Why vikunja_batch_import is rated Medium
This tool creates or modifies data (tasks) in a reversible manner, fitting the Write category. Severity is high because bulk imports can affect many tasks simultaneously and incorrect data could corrupt task state, though the damage is reversible. The dry-run support mentioned slightly mitigates risk but does not change the primary effect when executed without dry-run.
From the tool's definition Tool description states 'Import tasks in bulk from CSV or JSON formats' - import operations create or modify data (tasks) in the Vikunja instance. The bulk nature and file-based input increase the blast radius.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs vikunja_batch_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vikunja_batch_import, this is the rule to start with:
vikunja_batch_import 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 MCP Server, apply this rule, and every vikunja_batch_import call is checked against it from then on.
Questions about vikunja_batch_import
Import tasks in bulk from CSV or JSON formats with error handling and dry-run support. 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 vikunja_batch_import: 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.
vikunja_batch_import 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 vikunja_batch_import 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_batch_import. 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_batch_import is provided by the Vikunja MCP Server MCP server (democratize-technology/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vikunja MCP Server, and thousands of servers like it.
This server
Across the catalogue