New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_alert_slack_channels

Notifications triggered when cloud costs exceed defined thresholds or meet specific conditions. Lists Slack destinations eligible for Alert notifications for the authenticated customer and caller. Returns canonical identifiers for recipientsSlackChannels and integration status. User credentials i...

SERVERDoit SOURCE@doitintl/doit-mcp-server
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/list-alert-slack-channels.md

What list_alert_slack_channels does on Doit

AI agents call list_alert_slack_channels to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
pageToken string —
maxResults number —
nameContains string — Case-insensitive substring of the channel display name.
customerContext string — Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.

Parameters from the server's own tool schema.

Why list_alert_slack_channels is rated Low

Even though list_alert_slack_channels only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about list_alert_slack_channels

What does the list_alert_slack_channels tool do? +

Notifications triggered when cloud costs exceed defined thresholds or meet specific conditions. Lists Slack destinations eligible for Alert notifications for the authenticated customer and caller. Returns canonical identifiers for recipientsSlackChannels and integration status. User credentials include visible private channels; service accounts return public/shared channels only. Results are sorted by stable destination identity. Keep nameContains unchanged when following pageToken. This endpoint is paginated: a response with a non-empty pageToken has more results, returned when that value is passed as the pageToken parameter. A missing, null, or empty pageToken marks the last page. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.

What parameters does list_alert_slack_channels accept? +

list_alert_slack_channels accepts 4 parameters: pageToken, maxResults, nameContains, customerContext. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_alert_slack_channels? +

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

What risk level is list_alert_slack_channels? +

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

Can I rate-limit list_alert_slack_channels? +

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

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

list_alert_slack_channels is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Doit, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Doit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.