High-risk tools in Slack
4 of the 143 tools in Slack are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
SLACK_REGISTERS_A_NEW_CALL_WITH_PARTICIPANTSExecute 3/5DEPRECATED: Registers a new call in Slack using `calls.add` for third-party call integration. Use `start_call` instead.
-
SLACK_REGISTERS_NEW_CALL_PARTICIPANTSExecute 3/5DEPRECATED: Registers new participants added to a Slack call. Use `add_call_participants` instead.
-
SLACK_START_CALLExecute 3/5Registers a new call in Slack using `calls.add` for third-party call integration; `created_by` is required if not using a user-specific token.
-
SLACK_START_REAL_TIME_MESSAGING_SESSIONExecute 3/5Initiates a Slack RTM session providing a single-use WebSocket URL (valid 30s) for event streaming; does not set initial presence status.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Slack
Enforce policy on Slack
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init