conversations_rename

What conversations_rename does on Slack

AI agents use conversations_rename 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.

Why conversations_rename is rated Medium

Renaming a conversation modifies existing data (the channel name) but the change is reversible—it can be renamed again. This is a Write operation, not Destructive. Severity is medium because renaming channels could cause confusion in a workspace if done maliciously or carelessly, but the impact is limited to metadata and easily corrected. Confidence is high because the intent is unambiguous.

From the tool's definition Tool name 'conversations_rename' and description 'Rename a conversation' indicate modification of channel/conversation metadata. This creates a reversible change to Slack workspace structure.

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

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

Questions about conversations_rename