AI agents call slack_search to retrieve information from Access 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 existing Slack message data without modifying, deleting, or executing operations. It is categorized as Read. Severity is medium because: (1) it accesses potentially sensitive conversational data across all channels and DMs, which could expose confidential information if an AI agent searches for credentials, financial details, or private communications; (2) the blast radius includes…
From the tool's definition Tool description states it "Search[es] Slack messages" and "Returns matching messages"; the verb 'search' and 'returns' indicate data retrieval with no modification. No deletion, creation, or execution capability is described.
Attacks that exploit this kind of access
Search Slack messages across all channels and DMs using Slack search syntax. Use this to find specific conversations, mentions, or topics. Returns matching messages with channel context and timestamps. It is categorised as a Read tool in the Access MCP Server, which means it retrieves data without modifying state.
Register the Access MCP server in PolicyLayer and add a rule for slack_search: 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 Access. Nothing to install.
slack_search 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 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. 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 is provided by the Access MCP server (scottpedia0/access). 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 →