This record as markdown: /tools/0xk3vin-vikunja-mcp/buckets-create.md
What buckets_create does on Vikunja
AI agents use buckets_create 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 buckets_create is rated Medium
This tool creates a new bucket (a reversible modification to task/project organization). It does not execute code, delete data irreversibly, move money, or retrieve information. Creation of organizational elements in a task manager is a Write-category operation with low severity—misuse would only add unwanted buckets that can be deleted.
From the tool's definition Tool name 'buckets_create' and description 'Create a new kanban bucket' indicate creation of new data in a kanban board structure.
Attacks that exploit this kind of access
The rule that runs buckets_create 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 buckets_create, this is the rule to start with:
buckets_create 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 buckets_create call is checked against it from then on.
Questions about buckets_create
Create a new kanban bucket. 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 buckets_create: 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.
buckets_create 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 buckets_create 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 buckets_create. 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.
buckets_create 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