slack_action
Perform a Slack action: slack_send, slack_read, slack_search, slack_thread_reply, slack_channels, slack_react, slack_upload.
This record as markdown: /tools/creativelead-unclick/slack-action.md
What slack_action does on UnClick
AI agents invoke slack_action to trigger actions in UnClick. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | |
emoji | string | — | |
limit | number | — | |
query | string | — | |
action | string | — | |
channel | string | — | |
bot_token | string | — | |
thread_ts | string | — | |
timestamp | string | — |
Parameters from the server's own tool schema.
Why slack_action is rated High
This tool bundles multiple Slack operations including sending messages, replying to threads, reacting, and uploading files — all of which trigger external operations with real side effects. Since it spans Read, Write, and Execute categories, the most severe applicable is Execute.
From the tool's definition Perform a Slack action: slack_send, slack_read, slack_search, slack_thread_reply, slack_channels, slack_react, slack_upload
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs slack_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slack_action, this is the rule to start with:
slack_action stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every slack_action call is checked against it from then on.
Questions about slack_action
Perform a Slack action: slack_send, slack_read, slack_search, slack_thread_reply, slack_channels, slack_react, slack_upload. It is categorised as a Execute tool in the UnClick MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
slack_action accepts 9 parameters: text, emoji, limit, query, action, channel, bot_token, thread_ts, timestamp. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for slack_action: 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 UnClick. Nothing to install.
slack_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the slack_action 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 slack_action. 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.
slack_action is provided by the UnClick MCP server (creativelead/unclick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
Across the catalogue