Get all replies in a message thread. Get ts_slack from a message with reply_count > 0 (the thread parent). Replies may include files[] (attachments — each with id, name, mimetype, size); use download_slack_file with files[].id to download an attachment.
AI agents call get_slack_thread_replies 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 performs a read-only operation that retrieves conversation history from Slack. It queries thread replies and their associated metadata (attachments, timestamps) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an attacker could read private messages they might otherwise not have access to, but cannot alter, delete, or trigger external actions.
From the tool's definition Tool description states it 'Get[s] all replies in a message thread' and retrieves thread data including message metadata and file references. No modification, deletion, or execution occurs; the tool only retrieves and queries existing data.
Documented attack patterns abuse exactly the kind of access get_slack_thread_replies 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_thread_replies:
{
"version": "1",
"default": "deny",
"tools": {
"get_slack_thread_replies": {}
}
}get_slack_thread_replies 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.
Get all replies in a message thread. Get ts_slack from a message with reply_count > 0 (the thread parent). Replies may include files[] (attachments — each with id, name, mimetype, size); use download_slack_file with files[].id to download an attachment. 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_thread_replies: 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_thread_replies 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_thread_replies 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_thread_replies. 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_thread_replies 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.