slack_get_users
Get a list of all users in the workspace with their basic profile information
This record as markdown: /tools/slack/slack-get-users.md
What slack_get_users does on Slack
AI agents call slack_get_users 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.
Why slack_get_users is rated Low
This tool queries and retrieves a list of workspace users and their basic profile information. It performs no mutations, side effects, or destructive operations. While it exposes user information (a potential privacy concern), it remains a read-only operation. The severity is low because basic profile information is typically non-sensitive and discovery of user lists in a workspace is expected functionality.
From the tool's definition Tool name 'slack_get_users' and description 'Get a list of all users in the workspace with their basic profile information' indicate a retrieval operation that returns user data without modifying anything.
Attacks that exploit this kind of access
The rule that runs slack_get_users 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 slack_get_users, this is the rule to start with:
slack_get_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every slack_get_users call is checked against it from then on.
Questions about slack_get_users
Get a list of all users in the workspace with their basic profile information. It is categorised as a Read tool in the Slack MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP server in PolicyLayer and add a rule for slack_get_users: 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.
slack_get_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the slack_get_users 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.
Set action: deny in the PolicyLayer policy for slack_get_users. 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.
slack_get_users is provided by the Slack MCP server (@modelcontextprotocol/server-slack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Slack, and thousands of servers like it.
This server
Across the catalogue