team_external_teams_disconnect
Disconnect an external organization.
This record as markdown: /tools/karbassi-slack-mcp/team-external-teams-disconnect.md
What team_external_teams_disconnect does on Slack
AI agents call team_external_teams_disconnect to permanently remove resources in Slack, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why team_external_teams_disconnect is rated Critical
Disconnecting an external organization removes the linkage between Slack workspaces or organizations. This is an irreversible or very difficult to reverse operation with potentially broad impact, cutting off shared channels, cross-organization communication, and integrations. This falls under Destructive due to its permanent nature and high blast radius if misused.
From the tool's definition 'Disconnect an external organization' — disconnecting an external team/organization is an irreversible administrative action that severs cross-workspace relationships and cannot be easily undone.
Attacks that exploit this kind of access
The rule that runs team_external_teams_disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For team_external_teams_disconnect, this is the rule to start with:
team_external_teams_disconnect 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 Slack, apply this rule, and every team_external_teams_disconnect call is checked against it from then on.
Questions about team_external_teams_disconnect
Disconnect an external organization. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for team_external_teams_disconnect: 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 Slack. Nothing to install.
team_external_teams_disconnect 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 team_external_teams_disconnect 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 team_external_teams_disconnect. 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.
team_external_teams_disconnect is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Slack, and thousands of servers like it.
Across the catalogue