dnd_set_snooze

Turn on Do Not Disturb mode for the current user.

SERVERSlack SOURCEkarbassi/slack-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/dnd-set-snooze.md

WHAT IT DOES

What dnd_set_snooze does on Slack

AI agents use dnd_set_snooze to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.

RISK

Why dnd_set_snooze is rated Medium

This tool modifies user preferences/status in Slack by enabling Do Not Disturb mode. It is reversible (the user can disable it), affects only the current user's notification settings, and has no destructive, financial, or code execution implications. It qualifies as Write because it creates/modifies data (user status) without irreversible consequences.

From the tool's definition Tool name 'dnd_set_snooze' and description 'Turn on Do Not Disturb mode for the current user' indicate modification of user status settings. This creates/updates a reversible state change (Do Not Disturb mode) for the authenticated user.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dnd_set_snooze safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dnd_set_snooze, this is the rule to start with:

dnd_set_snooze Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dnd_set_snooze": {
      "limits": [
        {
          "counter": "dnd_set_snooze_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every dnd_set_snooze call is checked against it from then on.

FAQ

Questions about dnd_set_snooze

What does the dnd_set_snooze tool do? +

Turn on Do Not Disturb mode for the current user. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dnd_set_snooze? +

Register the Slack MCP server in PolicyLayer and add a rule for dnd_set_snooze: 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 dnd_set_snooze? +

dnd_set_snooze is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dnd_set_snooze? +

Yes. Add a rate_limit block to the dnd_set_snooze 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 dnd_set_snooze completely? +

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

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

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 233 Slack tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →