conversations_rename · Slack MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why conversations_rename needs a policy

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.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

conversations_rename Rate-limited

conversations_rename 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_rename": {
      "limits": [
        {
          "counter": "conversations_rename_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slack, so you can run agents against it safely.

FAQ

Questions about conversations_rename

What does the conversations_rename tool do? +

Rename 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_rename? +

Register the Slack MCP server in PolicyLayer and add a rule for conversations_rename: 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_rename? +

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

Can I rate-limit conversations_rename? +

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

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

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