slack_conversations_history

Get messages from a channel or direct message by channel_id

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/slack-conversations-history.md

WHAT IT DOES

What slack_conversations_history does on Sage MCP

AI agents call slack_conversations_history to retrieve information from Sage MCP 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_conversations_history is rated Low

This tool retrieves historical messages from Slack conversations. It performs a read-only query operation that does not modify, delete, or execute any actions. The only potential concern is that retrieved messages may contain sensitive information, but the tool itself has no destructive or state-changing capability.

From the tool's definition Tool name 'slack_conversations_history' and description 'Get messages from a channel or direct message by channel_id' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_conversations_history safely

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

slack_conversations_history Allowed

slack_conversations_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_conversations_history": {}
  }
}

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

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

FAQ

Questions about slack_conversations_history

What does the slack_conversations_history tool do? +

Get messages from a channel or direct message by channel_id. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on slack_conversations_history? +

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

What risk level is slack_conversations_history? +

slack_conversations_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit slack_conversations_history? +

Yes. Add a rate_limit block to the slack_conversations_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_conversations_history completely? +

Set action: deny in the PolicyLayer policy for slack_conversations_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_conversations_history? +

slack_conversations_history is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

The MCP Attack Database →

Guides

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