Reply to an existing message thread in Slack as yourself. PARAMETERS: channel, thread_ts, text. The thread_ts comes from ts_slack / thread_ts_slack on a message returned by get_slack_channel_history.
AI agents use reply_to_slack_thread to create or update resources in Apple Shortcuts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Shortcuts environment.
This tool posts a new message to a Slack thread, which is a reversible write action (messages can be deleted). It creates data in an external system but does not execute code, delete anything, or involve financial transactions. Severity is medium because a misused agent could post unwanted or harmful messages to Slack threads impersonating the user.
From the tool's definition Reply to an existing message thread in Slack as yourself
Documented attack patterns abuse exactly the kind of access reply_to_slack_thread 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 reply_to_slack_thread:
{
"version": "1",
"default": "deny",
"tools": {
"reply_to_slack_thread": {
"limits": [
{
"counter": "reply_to_slack_thread_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reply_to_slack_thread stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reply to an existing message thread in Slack as yourself. PARAMETERS: channel, thread_ts, text. The thread_ts comes from ts_slack / thread_ts_slack on a message returned by get_slack_channel_history. It is categorised as a Write tool in the Apple Shortcuts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for reply_to_slack_thread: 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.
reply_to_slack_thread is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reply_to_slack_thread 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 reply_to_slack_thread. 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.
reply_to_slack_thread 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.