dnd_end_snooze

End the current user's snooze mode.

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-end-snooze.md

WHAT IT DOES

What dnd_end_snooze does on Slack

AI agents use dnd_end_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_end_snooze is rated Medium

This tool modifies user notification/availability status by ending snooze mode. It is a Write action because it changes user state reversibly—the user can re-enter snooze mode if needed. It is not Execute (no code/command triggered), not Destructive (no permanent data loss), not Financial, and not Read (causes a state change).

From the tool's definition Tool name 'dnd_end_snooze' and description 'End the current user's snooze mode' indicate modification of user status/notification settings. The action reverses a temporary do-not-disturb state, making it a reversible state change rather than data retrieval.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs dnd_end_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_end_snooze, this is the rule to start with:

dnd_end_snooze Rate-limited

dnd_end_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_end_snooze": {
      "limits": [
        {
          "counter": "dnd_end_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_end_snooze call is checked against it from then on.

FAQ

Questions about dnd_end_snooze

What does the dnd_end_snooze tool do? +

End the current user's snooze mode. 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_end_snooze? +

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

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

Can I rate-limit dnd_end_snooze? +

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

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

dnd_end_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

The MCP Attack Database →

Guides

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