// SCAN REPORT

MCP Slack

15 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

15 read-only

15 tools total

Community server · catalogue entry verified 30/06/2026

How to control MCP Slack ↓

TOOL MAP

What MCP Slack exposes to your agents

Read (15) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control MCP Slack

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Slack, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "slack_auth_test": {
    "limits": [
      {
        "counter": "slack_auth_test_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Slack — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP SLACK →

Instant setup, no code required.

FULL CATALOGUE

All 15 MCP Slack tools

READ 15 tools

Read slack_auth_test Test Slack authentication and get info about the token owner. Read slack_get_channel_history slack_get_channel_history Read slack_get_channel_info Get detailed information about a Slack channel. Read slack_get_file_info Get metadata about a Slack file (no content download). Read slack_get_reactions Get reactions for a specific Slack message. Read slack_get_thread_replies slack_get_thread_replies Read slack_get_user_info Get information about a Slack user. Read slack_get_user_profile Get a Slack user's profile information. Read slack_list_channel_members List members of a Slack channel. Read slack_list_channels slack_list_channels Read slack_list_files slack_list_files Read slack_list_reactions slack_list_reactions Read slack_list_stars List starred items for the authenticated user. Read slack_list_users List users in the Slack workspace. Read slack_search_messages slack_search_messages

FAQ

Questions about MCP Slack

Is the MCP Slack MCP server safe to use without restrictions? +

The MCP Slack server is primarily read-only with 15 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the MCP Slack MCP server expose? +

15 tools across 1 categories: Read. 15 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on MCP Slack? +

Register the MCP Slack MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Slack tool call.

Deterministic rules across all 15 MCP Slack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP SLACK →

Instant setup, no code required.

15 MCP Slack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from MCP Slack's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →