AI agents call slack_search_messages to retrieve information from Slack MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries message data from Slack without modifying, deleting, or executing any actions. It is a search/query function that only returns existing information, making it a Read category tool with low severity since message search access is a standard, low-risk workspace capability.
From the tool's definition Tool description states 'Search for messages in the Slack workspace' and is grouped with read-only operations like 'slack_get_channel_history', 'slack_get_channels', and 'slack_get_users'. The function performs a query operation with no side effects.
Attacks that exploit this kind of access
Search for messages in the Slack workspace. It is categorised as a Read tool in the Slack MCP MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for slack_search_messages: 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. Nothing to install.
slack_search_messages 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_search_messages 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_search_messages. 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_search_messages is provided by the Slack MCP server (neilkuo-opennet/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 →