Permanently delete a Collective from the trash. THIS IS IRREVERSIBLE. The Collective must already be in the trash (use delete_collective first). Set deleteTeam=true to also remove the underlying Nextcloud Team.
AI agents call permanently_delete_collective to permanently remove resources in Collectives — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (a Collective and optionally associated Team) that cannot be recovered once executed. It operates on data already in trash but performs permanent removal. The explicit 'IRREVERSIBLE' warning and capability to also delete the underlying Team structure makes this critical severity. This is the most severe category applicable.
From the tool's definition Tool description explicitly states 'Permanently delete a Collective from the trash. THIS IS IRREVERSIBLE.' The operation removes a Collective and optionally its underlying Nextcloud Team, with no undo capability.
Attacks that exploit this kind of access
Permanently delete a Collective from the trash. THIS IS IRREVERSIBLE. The Collective must already be in the trash (use delete_collective first). Set deleteTeam=true to also remove the underlying Nextcloud Team. It is categorised as a Destructive tool in the Collectives MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Collectives MCP server in PolicyLayer and add a rule for permanently_delete_collective: 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 Collectives. Nothing to install.
permanently_delete_collective 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 permanently_delete_collective 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 permanently_delete_collective. 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.
permanently_delete_collective is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →