AI agents use create_task 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.
Creating a task is a reversible write operation that adds data to the system without irreversibly deleting data or executing arbitrary code. The action can be undone by deleting the task later.
From the tool's definition Tool name is 'create_task' and description states 'Create a task in a project' — this creates new data in the task management system.
Attacks that exploit this kind of access
Create a task in a project. 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 create_task: 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.
create_task 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 create_task 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 create_task. 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.
create_task is provided by the Vikunja MCP server (ugoi/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 →