get_channel_history
AI agents call get_channel_history 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 historical message data from a Slack channel. Retrieval operations that do not modify, delete, or execute actions are classified as Read. The lack of blast radius (no data modification, deletion, or external execution) justifies low severity. Confidence is reduced slightly due to empty description, but the name and context are clear.
From the tool's definition Tool name 'get_channel_history' indicates retrieval of historical messages from a Slack channel. The sibling tools on this server (get_channel_info, get_channel_members, get_user_info, list_channels, list_files, get_thread_replies) are all Read operations…
Attacks that exploit this kind of access
get_channel_history. 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_history: 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_history 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_history 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_history. 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_history 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 →