AI agents call slack_get_channel_history to retrieve information from Slackxmcp 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 Slack channels. It performs a read-only query operation with no side effects—it neither creates, modifies, deletes, executes commands, nor commits financial actions. The pagination and time-bound parameters are filtering options for the retrieval, not indicators of write or execute capabilities.
From the tool's definition Tool name 'slack_get_channel_history' and description 'Fetch messages from a Slack conversation with optional pagination and time bounds' indicate data retrieval with no modification or destructive capability.
Attacks that exploit this kind of access
Fetch messages from a Slack conversation with optional pagination and time bounds. It is categorised as a Read tool in the Slackxmcp MCP Server, which means it retrieves data without modifying state.
Register the Slackx 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 Slackxmcp. Nothing to install.
slack_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 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.
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.
slack_get_channel_history is provided by the Slackx MCP server (vaibhavpandeyvpz/slackxmcp). 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 →