circles_delete
Delete a circle/team. Requires owner privileges.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/circles-delete.md
What circles_delete does on AIquila — Nextcloud MCP Server
AI agents call circles_delete 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 |
|---|---|---|---|
circleId | string | Yes | The circle ID to delete |
Parameters from the server's own tool schema.
Why circles_delete is rated Critical
This tool irreversibly removes a circle or team from Nextcloud, which cannot be undone. It destroys organizational structures and potentially cascades effects (loss of shared files, permissions, collaboration contexts). While guarded by owner privileges, misuse by a compromised owner account or prompt injection could cause significant data loss.
From the tool's definition Tool name includes 'delete' and description states 'Delete a circle/team'. The action is irreversible—once a circle/team is deleted, associated data and membership structures are permanently removed.
Attacks that exploit this kind of access
The rule that runs circles_delete 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 circles_delete, this is the rule to start with:
circles_delete 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 circles_delete call is checked against it from then on.
Questions about circles_delete
Delete a circle/team. Requires owner privileges. 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.
circles_delete accepts 1 parameter: circleId. Required: circleId. 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 circles_delete: 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.
circles_delete 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 circles_delete 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 circles_delete. 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.
circles_delete 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