Get a list of all users in the workspace with their basic profile information
AI agents call slack_get_users to retrieve information from Server Puppeteer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries workspace user data and returns profile information without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal security impact unless the workspace contains sensitive user identifiers, but the basic nature of user directory information and lack of side effects classifies it as Read with low severity.
From the tool's definition Tool description states 'Get a list of all users in the workspace with their basic profile information' — a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get a list of all users in the workspace with their basic profile information. It is categorised as a Read tool in the Server Puppeteer MCP Server, which means it retrieves data without modifying state.
Register the Server Puppeteer 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 Server Puppeteer. 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 Server Puppeteer MCP server (@hisma/server-puppeteer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →