get_slack_unread_messages
Get unread messages in a channel based on your read position. Requires user authorization. Bot-only connections cannot track unread state. For private channels/DMs, set include_private=true (default false for safety). Returns most-recent-unread-first.
This record as markdown: /tools/freshdesk/get-slack-unread-messages.md
What get_slack_unread_messages does on Freshdesk
AI agents call get_slack_unread_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 get_slack_unread_messages is rated Low
This tool queries and retrieves existing Slack messages without creating, modifying, deleting, or executing any actions. It requires user authorization and respects channel privacy settings (include_private parameter), but fundamentally it is a read-only information retrieval function.
From the tool's definition Tool 'retrieves' unread messages in a channel based on read position; returns data without modification or side effects. Description explicitly states 'Get unread messages' and 'Returns most-recent-unread-first', indicating a query/fetch operation.
Attacks that exploit this kind of access
The rule that runs get_slack_unread_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 get_slack_unread_messages, this is the rule to start with:
get_slack_unread_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 get_slack_unread_messages call is checked against it from then on.
Questions about get_slack_unread_messages
Get unread messages in a channel based on your read position. Requires user authorization. Bot-only connections cannot track unread state. For private channels/DMs, set include_private=true (default false for safety). Returns most-recent-unread-first. 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 get_slack_unread_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.
get_slack_unread_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 get_slack_unread_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 get_slack_unread_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.
get_slack_unread_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