Generate a weekly review summary: overdue tasks, tasks due this week, high-priority open tasks, and recently completed tasks.
AI agents call weekly_review 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 only retrieves and aggregates existing task data to generate a summary report. It reads task states (overdue, due this week, high-priority, recently completed) without creating, modifying, or deleting any data. No side effects are implied.
From the tool's definition Generate a weekly review summary: overdue tasks, tasks due this week, high-priority open tasks, and recently completed tasks.
Attacks that exploit this kind of access
Generate a weekly review summary: overdue tasks, tasks due this week, high-priority open tasks, and recently completed tasks. 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 weekly_review: 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.
weekly_review 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 weekly_review 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 weekly_review. 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.
weekly_review 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 →