slack_get_channel_history
Get recent messages from a channel
Part of the Slack MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call slack_get_channel_history to retrieve information from Slack without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON SLACK_GET_CHANNEL_HISTORY
Even though slack_get_channel_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
slack_get_channel_history:
rules:
- action: allowSee the full Slack policy for all 8 tools.
DETAILS
MORE SLACK TOOLS
slack_get_thread_replies Read slack_get_user_profile Read slack_get_users Read slack_list_channels Read slack_add_reaction Write slack_post_message Write slack_reply_to_thread Other SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the slack_get_channel_history tool do?
Get recent messages from a channel. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
How do I enforce a policy on slack_get_channel_history?
Add a rule in your Intercept YAML policy under the tools section for slack_get_channel_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Slack MCP server.
What risk level is slack_get_channel_history?
slack_get_channel_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Can I rate-limit slack_get_channel_history?
Yes. Add a rate_limit block to the slack_get_channel_history rule in your Intercept 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 slack_get_channel_history completely?
Set action: deny in the Intercept policy for slack_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.
What MCP server provides slack_get_channel_history?
slack_get_channel_history is provided by the Slack MCP server (modelcontextprotocol/server-slack). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON SLACK
Open source. One binary. Zero dependencies.