conversations_leave

Leave a conversation.

SERVERSlack SOURCEkarbassi/slack-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/conversations-leave.md

WHAT IT DOES

What conversations_leave does on Slack

AI agents use conversations_leave to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.

RISK

Why conversations_leave is rated Medium

This tool modifies data (conversation membership) but the change is reversible. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions (would be Financial). It is a Write operation because it changes the state of a resource (the user's participation in a conversation).

From the tool's definition Tool name 'conversations_leave' and description 'Leave a conversation' indicate a reversible action that modifies the user's membership state in a Slack conversation. The change can be undone by rejoining the conversation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs conversations_leave 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 conversations_leave, this is the rule to start with:

conversations_leave Rate-limited

conversations_leave stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "conversations_leave": {
      "limits": [
        {
          "counter": "conversations_leave_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every conversations_leave call is checked against it from then on.

FAQ

Questions about conversations_leave

What does the conversations_leave tool do? +

Leave a conversation. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on conversations_leave? +

Register the Slack MCP server in PolicyLayer and add a rule for conversations_leave: 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.

What risk level is conversations_leave? +

conversations_leave is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit conversations_leave? +

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

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

conversations_leave 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.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →