projects_update

Update an existing project

SERVERVikunja SOURCE0xk3vin/vikunja-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xk3vin-vikunja-mcp/projects-update.md

WHAT IT DOES

What projects_update does on Vikunja

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

RISK

Why projects_update is rated Medium

This tool creates or modifies data reversibly by updating project attributes. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). The impact is confined to project metadata changes, making it a Write operation. Severity is medium because unauthorized project modifications could disrupt task management workflows and team coordination, but changes are reversible.

From the tool's definition Tool name 'projects_update' and description 'Update an existing project' indicate modification of existing data without deletion.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs projects_update safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vikunja, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For projects_update, this is the rule to start with:

projects_update Rate-limited

projects_update 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": {
    "projects_update": {
      "limits": [
        {
          "counter": "projects_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vikunja, apply this rule, and every projects_update call is checked against it from then on.

FAQ

Questions about projects_update

What does the projects_update tool do? +

Update an existing project. It is categorised as a Write tool in the Vikunja MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on projects_update? +

Register the Vikunja MCP server in PolicyLayer and add a rule for projects_update: 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.

What risk level is projects_update? +

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

Can I rate-limit projects_update? +

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

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

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

KEEP EXPLORING

More on Vikunja, and thousands of servers like it.

This server

All 31 Vikunja tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →