circles_delete

Delete a circle/team. Requires owner privileges.

Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Why circles_delete is rated Critical

This tool permanently removes a circle/team entity and cannot be undone. Deletion is irreversible and destroys data, placing it in the Destructive category. Severity is high because deleting a team affects multiple users and shared resources, though it requires owner privileges which limits blast radius somewhat. Not critical because the privilege requirement provides some guardrail against casual misuse.

From the tool's definition Tool name 'circles_delete' and description 'Delete a circle/team' explicitly perform irreversible deletion of a data structure (circle/team). The requirement for 'owner privileges' indicates administrative scope.

Questions about circles_delete

What does the circles_delete tool do? +

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.

How do I enforce a policy on circles_delete? +

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.

What risk level is circles_delete? +

circles_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit circles_delete? +

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.

How do I block circles_delete completely? +

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.

What MCP server provides circles_delete? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of AIquila — Nextcloud MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.