List Slack channels the bot has access to
AI agents call slack_list_channels to retrieve information from Slack MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of channel metadata. There is minimal security risk as it only exposes information about channels the bot already has access to, with no capability to create, modify, delete, or execute actions. The blast radius of misuse is limited to information disclosure of channel names and basic metadata.
From the tool's definition Tool name 'slack_list_channels' and description 'List Slack channels the bot has access to' indicate a retrieval operation with no side effects. It queries available channels without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
List Slack channels the bot has access to. It is categorised as a Read tool in the Slack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for slack_list_channels: 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 MCP Server. Nothing to install.
slack_list_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the slack_list_channels 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 slack_list_channels. 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.
slack_list_channels is provided by the Slack MCP Server MCP server (sdancy10/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →