complete_task
Mark a task as completed or reopen it. Sets STATUS, PERCENT-COMPLETE, and COMPLETED date atomically.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/complete-task.md
What complete_task does on AIquila — Nextcloud MCP Server
AI agents use complete_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.
Why complete_task is rated Medium
This tool modifies task state in a Nextcloud system by updating multiple fields. While the changes are reversible (a completed task can be reopened), it still constitutes a write operation that alters data. The severity is medium because task status changes could affect workflows and notifications, but the impact is limited to a single task entity and is not destructive or irreversible.
From the tool's definition Tool description states it 'Mark a task as completed or reopen it' and 'Sets STATUS, PERCENT-COMPLETE, and COMPLETED date atomically' — these are modifications to task data that are reversible (tasks can be reopened).
Attacks that exploit this kind of access
The rule that runs complete_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 complete_task, this is the rule to start with:
complete_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.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every complete_task call is checked against it from then on.
Questions about complete_task
Mark a task as completed or reopen it. Sets STATUS, PERCENT-COMPLETE, and COMPLETED date atomically. 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.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for complete_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.
complete_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the complete_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 complete_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.
complete_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.
This server
Across the catalogue