Slackワークスペース内のチャンネル一覧を取得
AI agents call 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 retrieves information about channels in a Slack workspace with no side effects. It is a read-only operation that fetches data from the workspace. The only potential concern is information disclosure (learning about channel structure), but this is minimal in most Slack workspaces where channel lists are typically discoverable. This is a standard Read category tool with low severity.
From the tool's definition Tool name 'list_channels' and description 'Slackワークスペース内のチャンネル一覧を取得' (retrieve list of channels in Slack workspace) indicate querying/listing data without modification.
Attacks that exploit this kind of access
Slackワークスペース内のチャンネル一覧を取得. 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 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.
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 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 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.
list_channels is provided by the Slack MCP Server MCP server (miyatsuki/study-slack-remote-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 →