Soft-delete a Collective (moves it to the Collectives trash, recoverable). Use permanently_delete_collective to remove it permanently and optionally delete the underlying Team.
AI agents call 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.
Although the deletion is soft (recoverable from trash), this tool irreversibly removes a Collective from normal access and operation. The description explicitly mentions it 'moves it to trash' and references a separate 'permanently_delete_collective' function for true permanent removal, confirming this is a destructive action.
From the tool's definition Tool name is 'delete_collective' and description states it 'Soft-delete a Collective (moves it to the Collectives trash, recoverable)'.
Attacks that exploit this kind of access
Soft-delete a Collective (moves it to the Collectives trash, recoverable). Use permanently_delete_collective to remove it permanently and optionally delete the underlying 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 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.
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 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 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.
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 →