New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_team_collaboration

Delete a team collaboration session. This cannot be undone.

SERVERAutomagik Tools SOURCEnamastexlabs/automagik-tools
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/namastexlabs-automagik-tools/delete-team-collaboration.md

What delete_team_collaboration does on Automagik Tools

AI agents call delete_team_collaboration to permanently remove resources in Automagik Tools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_team_collaboration is rated Critical

The tool permanently deletes a team collaboration session with no recovery option. This is irreversible data destruction, which is the defining characteristic of the Destructive category. The severity is high because deleting a collaboration session could affect multiple team members' work and access to shared resources, though it is scoped to a single session rather than critical infrastructure.

From the tool's definition Tool name is 'delete_team_collaboration' and description explicitly states 'This cannot be undone', indicating irreversible deletion of data.

Questions about delete_team_collaboration

What does the delete_team_collaboration tool do? +

Delete a team collaboration session. This cannot be undone. It is categorised as a Destructive tool in the Automagik Tools 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 delete_team_collaboration? +

Register the Automagik Tools MCP server in PolicyLayer and add a rule for delete_team_collaboration: 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 Automagik Tools. Nothing to install.

What risk level is delete_team_collaboration? +

delete_team_collaboration 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 delete_team_collaboration? +

Yes. Add a rate_limit block to the delete_team_collaboration 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 delete_team_collaboration completely? +

Set action: deny in the PolicyLayer policy for delete_team_collaboration. 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 delete_team_collaboration? +

delete_team_collaboration is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Automagik Tools, 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 Automagik Tools'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.