update_task

Update an existing task's fields by UID. Uses CalDAV ETag-based optimistic concurrency.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-task.md

WHAT IT DOES

What update_task does on AIquila — Nextcloud MCP Server

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

Parameter	Type	Required	Description
`due`	object	—	New due date (YYYYMMDD or YYYYMMDDTHHmmssZ), or null to remove
`uid`	string	Yes	The UID of the task to update
`url`	object	—	New URL, or null to remove
`pinned`	boolean	—	Pin or unpin the task
`status`	string	—	New status
`dtstart`	object	—	New start date, or null to remove
`summary`	string	—	New task title
`location`	object	—	New location, or null to remove
`priority`	number	—	New priority (0-9, 0 removes priority)
`relatedTo`	object	—	New parent UID, or null to remove parent
`categories`	array	—	Replace all tags with these
`description`	string	—	New description

Parameters from the server's own tool schema.

RISK

Why update_task is rated Medium

This tool creates or modifies data reversibly—it updates task fields rather than deleting or destroying them. While it operates on a calendar/task management system (part of Nextcloud), the operation is fundamentally a Write action. Severity is medium because task updates are reversible and generally have limited blast radius, though careless modifications could affect scheduling or planning workflows.

From the tool's definition Tool name 'update_task' and description 'Update an existing task's fields by UID' indicate modification of existing data. The CalDAV ETag-based concurrency mechanism confirms this is a reversible write operation on task records.

Risk signalsAccepts URL/endpoint input (url) · High parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_task safely

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

update_task Rate-limited

update_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": {
    "update_task": {
      "limits": [
        {
          "counter": "update_task_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 AIquila — Nextcloud MCP Server, apply this rule, and every update_task call is checked against it from then on.

FAQ

Questions about update_task

What does the update_task tool do? +

Update an existing task's fields by UID. Uses CalDAV ETag-based optimistic concurrency. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_task accept? +

update_task accepts 12 parameters: due, uid, url, pinned, status, dtstart, summary, location, priority, relatedTo, categories, description. Required: uid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_task? +

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

What risk level is update_task? +

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

Can I rate-limit update_task? +

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

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

update_task is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →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 →