AI agents call vikunja_list_tasks to retrieve information from Vikunja without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task data without creating, modifying, deleting, or executing operations. It is a read-only operation that retrieves information from the Vikunja task management system. The optional parameters (search, filtering, sorting, expansions) are all read-only query modifiers with no side effects. Low severity because misuse would only expose task data that the user already has access to.
From the tool's definition Tool name is 'vikunja_list_tasks' and description states it 'List tasks across all accessible projects, with optional search, filtering, sorting, and expansions.' The verb 'list' and operation of retrieving/querying tasks with no mention of modifications,…
Attacks that exploit this kind of access
List tasks across all accessible projects, with optional search, filtering, sorting, and expansions. It is categorised as a Read tool in the Vikunja MCP Server, which means it retrieves data without modifying state.
Register the Vikunja MCP server in PolicyLayer and add a rule for vikunja_list_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. Nothing to install.
vikunja_list_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vikunja_list_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 vikunja_list_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.
vikunja_list_tasks is provided by the Vikunja MCP server (shichao402/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 →