Low Risk

SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS

DEPRECATED: Retrieves a user's current Do Not Disturb status. Use `get_team_dnd_status` instead.

Part of the Slack MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS to retrieve information from Slack without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

slack.yaml
tools:
  SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS:
    rules:
      - action: allow

See the full Slack policy for all 143 tools.

Tool Name SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS
Category Read
MCP Server Slack MCP Server
Risk Level Low

View all 143 tools →

Agents calling read-class tools like SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS tool do? +

DEPRECATED: Retrieves a user's current Do Not Disturb status. Use `get_team_dnd_status` instead.. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS? +

Add a rule in your Intercept YAML policy under the tools section for SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Slack MCP server.

What risk level is SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS? +

SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS? +

Yes. Add a rate_limit block to the SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS rule in your Intercept 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 SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS completely? +

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

SLACK_FETCH_DND_STATUS_FOR_MULTIPLE_TEAM_MEMBERS is provided by the Slack MCP server (@modelcontextprotocol/server-slack). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Slack

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.