Low Risk

list_channel_members

List all members of a specific channel, including their permissions and join information

How to control list_channel_members ↓

What list_channel_members does on Claude Slack

AI agents call list_channel_members to retrieve information from Claude Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_channel_members needs a policy

This tool queries and returns information about channel membership and permissions without modifying, deleting, executing, or creating anything. It is a straightforward data retrieval operation analogous to 'get' or 'list' functions. The blast radius is minimal since listing members reveals only metadata about team structure that is typically already visible to channel participants.

From the tool's definition Tool name 'list_channel_members' and description 'List all members of a specific channel, including their permissions and join information' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access list_channel_members gives an agent:

How to control list_channel_members

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Slack, and nothing reaches the server without passing your rules. This is the rule we recommend for list_channel_members:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_channel_members": {}
  }
}

list_channel_members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Slack — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_channel_members

What does the list_channel_members tool do? +

List all members of a specific channel, including their permissions and join information. It is categorised as a Read tool in the Claude Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_channel_members? +

Register the Claude Slack MCP server in PolicyLayer and add a rule for list_channel_members: 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 Claude Slack. Nothing to install.

What risk level is list_channel_members? +

list_channel_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_channel_members? +

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

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

list_channel_members is provided by the Claude Slack MCP server (theo-nash/claude-slack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Slack tool call.

Start from Claude Slack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.