Get a list of all users in the workspace with their basic profile information
AI agents call slack_get_users to retrieve information from Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation. It queries and returns user information but does not create, modify, delete, execute code, or have any destructive effects. It maps to the Read category as a simple GET-like operation.
From the tool's definition Tool name is 'slack_get_users' and description states 'Get a list of all users in the workspace with their basic profile information' — retrieves user data with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access slack_get_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slack, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_get_users:
{
"version": "1",
"default": "deny",
"tools": {
"slack_get_users": {}
}
}slack_get_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 (zencoderai/slack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Slack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Slack tools catalogued and risk-classified — across an index of 42,500+ MCP servers.