Get detailed information about a channel.
AI agents call get_channel_info 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 channel metadata without modifying, deleting, or executing any operations. It is a straightforward read operation that queries Slack channel information. The sibling tools (get_channel_history, get_channel_members, list_channels, etc.) confirm this server's read-oriented tools.
From the tool's definition Tool name is 'get_channel_info' and description states 'Get detailed information about a channel.' The verb 'get' and the retrieval-only nature of fetching channel metadata indicates no side effects.
Attacks that exploit this kind of access
Get detailed information about a channel. 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_channel_info: 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_channel_info 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_channel_info 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_channel_info. 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_channel_info is provided by the Slack MCP Server MCP server (software-engineer-mj/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 →