This record as markdown: /tools/0xk3vin-vikunja-mcp/labels-create.md
What labels_create does on Vikunja
AI agents use labels_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 labels_create is rated Medium
This tool creates a new label, which is a reversible write operation. It modifies the system state by adding data but does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because creating labels is a normal operation but could clutter the system if misused by an agent without proper constraints.
From the tool's definition Tool name 'labels_create' and description 'Create a new label' clearly indicate this tool creates new data in the Vikunja task manager system.
Attacks that exploit this kind of access
The rule that runs labels_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 labels_create, this is the rule to start with:
labels_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 labels_create call is checked against it from then on.
Questions about labels_create
Create a new label. 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 labels_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.
labels_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 labels_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 labels_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.
labels_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