move_project · Vikunja MCP Server MCP: Risk & Policy

WHAT IT DOES

What move_project does on Vikunja MCP Server

AI agents use move_project 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 move_project needs a policy

Moving a project changes its metadata (parent and position) but does not delete, destroy, or irreversibly alter data. It is a reversible structural modification, fitting the Write category. Severity is medium because misuse could disrupt project organization and visibility for teams, but the action itself is non-destructive and can be undone.

From the tool's definition Tool description states 'Move a project to a different parent or position' — a modification operation that reorganizes project hierarchy without deleting or destroying data. The action is reversible: projects can be moved back to their original location.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move_project Rate-limited

move_project 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": {
    "move_project": {
      "limits": [
        {
          "counter": "move_project_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 move_project

What does the move_project tool do? +

Move a project to a different parent or position. 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 move_project? +

Register the Vikunja MCP Server MCP server in PolicyLayer and add a rule for move_project: 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 move_project? +

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

Can I rate-limit move_project? +

Yes. Add a rate_limit block to the move_project 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 move_project completely? +

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

move_project is provided by the Vikunja MCP Server MCP server (wosh-i/vikunja-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.