slack_users_list

List all users in the workspace

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/slack-users-list.md

WHAT IT DOES

What slack_users_list does on Sage MCP

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

RISK

Why slack_users_list is rated Low

This tool retrieves and enumerates all users in a Slack workspace. While it performs no modifications, it exposes sensitive information (user identities, potentially email addresses, profiles) across an entire workspace, making it a Read operation with medium severity due to information disclosure risk if misused by an agent to profile users or extract organizational structure.

From the tool's definition Tool name 'slack_users_list' and description 'List all users in the workspace' indicate a query operation that retrieves user data without modifying anything.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_users_list safely

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

slack_users_list Allowed

slack_users_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": {
    "slack_users_list": {}
  }
}

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

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

FAQ

Questions about slack_users_list

What does the slack_users_list tool do? +

List all users in the workspace. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on slack_users_list? +

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

What risk level is slack_users_list? +

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

Can I rate-limit slack_users_list? +

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

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

slack_users_list is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage 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 →