get_slack_message_by_link
Retrieve a Slack message from its permalink URL. Supports standard permalinks (workspace.slack.com/archives/...), thread permalinks (?thread_ts=...), and app URLs (app.slack.com/client/...). For thread messages, returns the message and surrounding thread context (set include_thread=false to skip)...
This record as markdown: /tools/freshdesk/get-slack-message-by-link.md
What get_slack_message_by_link does on Freshdesk
AI agents call get_slack_message_by_link 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_message_by_link is rated Low
This tool only retrieves existing Slack message data using a URL permalink. It has no side effects, does not modify data, and does not trigger external operations. The 'include_thread' parameter only controls what read data is returned, not whether data is modified.
From the tool's definition Tool name contains 'get_' and description states 'Retrieve a Slack message from its permalink URL' with no modification or deletion capabilities mentioned. It only reads message data and thread context.
Attacks that exploit this kind of access
The rule that runs get_slack_message_by_link 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_message_by_link, this is the rule to start with:
get_slack_message_by_link 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_message_by_link call is checked against it from then on.
Questions about get_slack_message_by_link
Retrieve a Slack message from its permalink URL. Supports standard permalinks (workspace.slack.com/archives/...), thread permalinks (?thread_ts=...), and app URLs (app.slack.com/client/...). For thread messages, returns the message and surrounding thread context (set include_thread=false to skip). Prefers user token (broader read access to public channels). 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_message_by_link: 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_message_by_link 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_message_by_link 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_message_by_link. 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_message_by_link 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