List tasks across all projects, with optional filtering and search. Filter syntax examples: done = false priority >= 3 && done = false due_date < now && done = false (overdue) due_date > now && due_date < now+7d (due this week) project_id = 5 Sort options: id, title, done, done_at, due_date, crea...
AI agents call list_tasks to retrieve information from Vikunja MCP Server 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 modifying, deleting, or executing any operations. The filtering and sorting capabilities are purely for data retrieval. There is no mechanism to create, update, delete, or execute code. This is a straightforward Read category tool with low severity due to its passive, informational nature.
From the tool's definition Tool name is 'list_tasks' and description states it 'List tasks across all projects, with optional filtering and search.' The only operations described are listing, filtering, and searching—all read-only operations with no side effects on data.
Attacks that exploit this kind of access
List tasks across all projects, with optional filtering and search. Filter syntax examples: done = false priority >= 3 && done = false due_date < now && done = false (overdue) due_date > now && due_date < now+7d (due this week) project_id = 5 Sort options: id, title, done, done_at, due_date, created, updated, priority, position. It is categorised as a Read tool in the Vikunja MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for 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 MCP Server. Nothing to install.
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 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 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.
list_tasks is provided by the Vikunja MCP Server MCP server (lindenlion/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 →