reopen_task · Vikunja MCP Server MCP: Risk & Policy

WHAT IT DOES

What reopen_task does on Vikunja MCP Server

AI agents use reopen_task to create or update resources in Vikunja MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vikunja MCP Server environment.

WHY IT NEEDS A POLICY

Why reopen_task needs a policy

The tool changes task completion status in a reversible manner (a task can be completed again later). This is clearly a Write operation (modifies data) rather than Read (no query), Execute (no code/command execution), Destructive (fully reversible), or Financial.

From the tool's definition Tool description states 'Mark a task as not done (reopen it)' — this modifies task state from completed to incomplete, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reopen_task Rate-limited

reopen_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reopen_task": {
      "limits": [
        {
          "counter": "reopen_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Vikunja MCP Server, so you can run agents against it safely.

FAQ

Questions about reopen_task

What does the reopen_task tool do? +

Mark a task as not done (reopen it). It is categorised as a Write tool in the Vikunja MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on reopen_task? +

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

What risk level is reopen_task? +

reopen_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reopen_task? +

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

How do I block reopen_task completely? +

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

What MCP server provides reopen_task? +

reopen_task 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.