Find channels by partial match on name/topic/purpose using conversations.list and local filtering.
AI agents call search_channels to retrieve information from Slack Max API MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves channel information through filtering and searching without creating, modifying, deleting, or executing any operations. It has no side effects and presents minimal risk even if misused by an AI agent, as it only returns existing channel metadata visible within the agent's workspace access level.
From the tool's definition Tool description states it 'Find channels by partial match on name/topic/purpose' which is a query operation with no modification of data. The underlying API method 'conversations.list' is a standard retrieval endpoint.
Attacks that exploit this kind of access
Find channels by partial match on name/topic/purpose using conversations.list and local filtering. It is categorised as a Read tool in the Slack Max API MCP MCP Server, which means it retrieves data without modifying state.
Register the Slack Max API MCP server in PolicyLayer and add a rule for search_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 Max API MCP. Nothing to install.
search_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 search_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 search_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.
search_channels is provided by the Slack Max API MCP server (jeongwoobin335/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 →