get_slack_channels
AI agents call get_slack_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 retrieves or enumerates Slack channels, which is a read-only operation with no side effects. It returns data without modifying, deleting, or executing anything. The low severity reflects minimal blast radius—an AI agent using this tool can at most discover channel information, which is not destructive or harmful.
From the tool's definition Tool name 'get_slack_channels' indicates a retrieval operation. Sibling tools include read operations like 'get_file_preview', 'get_slack_channel_history', 'get_slack_users', and 'get_workspace_info', establishing a pattern of information retrieval.
Attacks that exploit this kind of access
get_slack_channels. 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 get_slack_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.
get_slack_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 get_slack_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 get_slack_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.
get_slack_channels is provided by the Slack MCP Server MCP server (yeoamlog/slack-mcp-server). 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 →