slack_get_channel_history

Get message history from a Slack channel

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/slack-get-channel-history.md

WHAT IT DOES

What slack_get_channel_history does on ScopeGate

AI agents call slack_get_channel_history to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why slack_get_channel_history is rated Low

This tool retrieves message data from Slack channels. Although it accesses communication history which may contain sensitive information (medium severity due to potential data sensitivity), the operation itself is read-only with no destructive, modifying, or executable side effects. The blast radius is limited to information disclosure of already-existing messages.

From the tool's definition Tool name 'slack_get_channel_history' and description 'Get message history from a Slack channel' indicate retrieval of historical messages without modification or deletion. The action is a query/fetch operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_get_channel_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slack_get_channel_history, this is the rule to start with:

slack_get_channel_history Allowed

slack_get_channel_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slack_get_channel_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every slack_get_channel_history call is checked against it from then on.

FAQ

Questions about slack_get_channel_history

What does the slack_get_channel_history tool do? +

Get message history from a Slack channel. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on slack_get_channel_history? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for slack_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 ScopeGate. Nothing to install.

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 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.

How do I block slack_get_channel_history completely? +

Set action: deny in the PolicyLayer 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 ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →