search_slack_messages
Search messages across all channels in the Slack workspace. Requires user authorization (search:read scope). Supports Slack search modifiers: - from:@username — Messages from a specific user - in:#channel — Messages in a specific channel - before:YYYY-MM-DD / after:YYYY-MM-DD — Date filters - has...
This record as markdown: /tools/freshdesk/search-slack-messages.md
What search_slack_messages does on Freshdesk
AI agents call search_slack_messages to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why search_slack_messages is rated Low
This tool queries and retrieves data (Slack messages) without modifying, deleting, or executing actions. It is purely informational. Severity is medium rather than low because searching across all channels in a workspace could expose sensitive messages (PII, confidential discussions, private conversations) depending on workspace permissions and what the AI agent searches for, creating potential information…
From the tool's definition Tool description states it "Search[es] messages across all channels in the Slack workspace" and "Requires user authorization (search:read scope)". The word 'search' and 'read' scope confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_slack_messages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_slack_messages, this is the rule to start with:
search_slack_messages is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every search_slack_messages call is checked against it from then on.
Questions about search_slack_messages
Search messages across all channels in the Slack workspace. Requires user authorization (search:read scope). Supports Slack search modifiers: - from:@username — Messages from a specific user - in:#channel — Messages in a specific channel - before:YYYY-MM-DD / after:YYYY-MM-DD — Date filters - has:link / has:reaction — Content filters Set to_me=true to prepend. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for search_slack_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 Freshdesk. Nothing to install.
search_slack_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 search_slack_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 search_slack_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.
search_slack_messages is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Freshdesk, and thousands of servers like it.
This server
Across the catalogue