Low Risk

crow_vikunja_tasks

List tasks in a Vikunja project with optional filters

How to control crow_vikunja_tasks ↓

What crow_vikunja_tasks does on Crow

AI agents call crow_vikunja_tasks to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why crow_vikunja_tasks needs a policy

This tool queries and retrieves task data from a Vikunja project management system. The use of 'List' combined with 'optional filters' clearly indicates a read-only operation that retrieves data without side effects. No data is created, modified, deleted, or destroyed. The blast radius of misuse is limited to information disclosure.

From the tool's definition Tool name and description indicate 'List tasks' which is a read-only retrieval operation with optional filtering. No modifications, deletions, or external code execution are implied.

Documented attack patterns abuse exactly the kind of access crow_vikunja_tasks gives an agent:

How to control crow_vikunja_tasks

PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_vikunja_tasks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crow_vikunja_tasks": {}
  }
}

crow_vikunja_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crow_vikunja_tasks

What does the crow_vikunja_tasks tool do? +

List tasks in a Vikunja project with optional filters. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crow_vikunja_tasks? +

Register the Crow MCP server in PolicyLayer and add a rule for crow_vikunja_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 Crow. Nothing to install.

What risk level is crow_vikunja_tasks? +

crow_vikunja_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crow_vikunja_tasks? +

Yes. Add a rate_limit block to the crow_vikunja_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.

How do I block crow_vikunja_tasks completely? +

Set action: deny in the PolicyLayer policy for crow_vikunja_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.

What MCP server provides crow_vikunja_tasks? +

crow_vikunja_tasks is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Crow tool call.

Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.