list_slack_channels
List all channels in the connected Slack workspace. WARNING: channel_name filter only applies to the current page. For workspaces with 100+ channels, use list_slack_channels with limit=1000 and paginate via cursor, OR pass #channel-name directly to get_slack_channel_history (which auto-paginates ...
This record as markdown: /tools/freshdesk/list-slack-channels.md
What list_slack_channels does on Freshdesk
AI agents call list_slack_channels to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_slack_channels is rated Low
This tool retrieves channel metadata from Slack without creating, modifying, or deleting any data. It is a straightforward read operation that enumerates existing channels. The severity is low because even if an AI agent calls this tool repeatedly or exposes channel names, the impact is limited to information disclosure of channel existence, which is typically already discoverable to workspace members.
From the tool's definition Tool name 'list_slack_channels' and description 'List all channels in the connected Slack workspace' indicates a query/retrieval operation with no side effects. The warning about pagination and filtering confirms it is a retrieval-only function.
Attacks that exploit this kind of access
The rule that runs list_slack_channels safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_slack_channels, this is the rule to start with:
list_slack_channels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every list_slack_channels call is checked against it from then on.
Questions about list_slack_channels
List all channels in the connected Slack workspace. WARNING: channel_name filter only applies to the current page. For workspaces with 100+ channels, use list_slack_channels with limit=1000 and paginate via cursor, OR pass #channel-name directly to get_slack_channel_history (which auto-paginates the lookup). It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for list_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 Freshdesk. Nothing to install.
list_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 list_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 list_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.
list_slack_channels is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue