delete_task
Delete a task from Nextcloud Tasks by UID. This action is irreversible.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/delete-task.md
What delete_task does on AIquila — Nextcloud MCP Server
AI agents call delete_task to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
uid | string | Yes | The UID of the task to delete |
calendarName | string | — | The calendar name (default: 'tasks') |
Parameters from the server's own tool schema.
Why delete_task is rated Critical
Deleting a task is an irreversible operation that permanently removes data from Nextcloud Tasks. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' While the blast radius is limited to a single task (not system-wide), the irreversible nature and explicit statement of irreversibility warrant 'high' severity.
From the tool's definition Tool description explicitly states 'Delete a task' and 'This action is irreversible.' The function name 'delete_task' combined with the irreversible deletion semantics clearly indicates destructive behavior.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_task, this is the rule to start with:
delete_task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every delete_task call is checked against it from then on.
Questions about delete_task
Delete a task from Nextcloud Tasks by UID. This action is irreversible. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_task accepts 2 parameters: uid, calendarName. Required: uid. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for delete_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.
delete_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_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.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
Across the catalogue