AI agents call get_task 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 a single task object by its identifier. It performs no creation, modification, deletion, or external execution. It is a standard read operation consistent with the Read category, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_task' and description 'Get a single task by ID' indicate data retrieval without modification or side effects.
Attacks that exploit this kind of access
Get a single task by ID. 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 get_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.
get_task 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 get_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 get_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.
get_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 →