workflows_triggers_list

A read tool on the Slack MCP server.

SERVERSlack SOURCEkarbassi/slack-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/karbassi-slack-mcp/workflows-triggers-list.md

WHAT IT DOES

What workflows_triggers_list does on Slack

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

RISK

Why workflows_triggers_list is rated Low

Despite empty description, the '_list' suffix and context within the Slack MCP server's read/query tools indicate this retrieves workflow trigger information without modifying data. However, confidence is moderated (0.75) due to missing description.

From the tool's definition Tool name contains 'list' suffix and is part of a Slack MCP server that provides read-only access patterns like 'search', 'activity_feed', and other query operations. The '_list' naming convention strongly suggests retrieval of workflow trigger metadata.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

workflows_triggers_list Allowed

workflows_triggers_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workflows_triggers_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about workflows_triggers_list

What does the workflows_triggers_list tool do? +

workflows_triggers_list is a read tool on the Slack MCP server. 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 workflows_triggers_list? +

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

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

Can I rate-limit workflows_triggers_list? +

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

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

workflows_triggers_list 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

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →