client_boot · Slack MCP: Risk & Policy

WHAT IT DOES

What client_boot does on Slack

AI agents invoke client_boot to trigger actions in Slack. 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.

WHY IT NEEDS A POLICY

Why client_boot needs a policy

Booting a Slack client triggers an external operation (session initialization) with potentially broad side effects. The 'undocumented session endpoint' language raises concern: undocumented APIs are unpredictable and may have hidden consequences (e.g., invalidating other sessions, triggering auth flows, or exposing tokens). This goes beyond a simple read and constitutes an Execute-level action.

From the tool's definition 'Boot the Slack client (undocumented session endpoint)' — initiates a session/client boot operation via an undocumented endpoint

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

client_boot Rate-limited

client_boot 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "client_boot": {
      "limits": [
        {
          "counter": "client_boot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Slack, so you can run agents against it safely.

FAQ

Questions about client_boot

What does the client_boot tool do? +

Boot the Slack client (undocumented session endpoint). It is categorised as a Execute tool in the Slack MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on client_boot? +

Register the Slack MCP server in PolicyLayer and add a rule for client_boot: 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 Slack. Nothing to install.

What risk level is client_boot? +

client_boot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit client_boot? +

Yes. Add a rate_limit block to the client_boot 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.

How do I block client_boot completely? +

Set action: deny in the PolicyLayer policy for client_boot. 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.

What MCP server provides client_boot? +

client_boot is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.