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)...
AI agents call get_slack_message_by_link to retrieve information from Apple Shortcuts 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 Slack message data without any side effects. It performs information retrieval only—fetching message content, attachments metadata, and thread context via permalink URLs. No data is created, modified, deleted, or executed. This is a classic Read operation with minimal blast radius if misused (exposure of message content that the AI already has permission to access via the Slack API).
From the tool's definition Tool "Retrieve a Slack message from its permalink URL" with capabilities to return message content and thread context.
Documented attack patterns abuse exactly the kind of access get_slack_message_by_link gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for get_slack_message_by_link:
{
"version": "1",
"default": "deny",
"tools": {
"get_slack_message_by_link": {}
}
}get_slack_message_by_link is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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). Messages may include files[] (attachments — each with id, name, mimetype, size); use download_slack_file with files[].id to download an attachment. When the linked message is a thread parent, the response includes reply_count; call get_slack_thread_replies (with the parent ts) to read the replies. Prefers user token (broader read access to public channels). It is categorised as a Read tool in the Apple Shortcuts MCP Server, which means it retrieves data without modifying state.
Register the Apple Shortcuts 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 Apple Shortcuts. 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 Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.