워크스페이스의 모든 사용자 목록 조회
AI agents call slack_get_users to retrieve information from MCP Slack Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from a Slack workspace without modifying, creating, or deleting any data. It is a standard list/query operation that returns existing data. The severity is low because user roster information is typically non-sensitive metadata in most organizational contexts, and the tool performs no destructive, financial, or code-execution operations.
From the tool's definition Tool name 'slack_get_users' and description '워크스페이스의 모든 사용자 목록 조회' (retrieves a list of all users in the workspace) indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
워크스페이스의 모든 사용자 목록 조회. It is categorised as a Read tool in the MCP Slack Python MCP Server, which means it retrieves data without modifying state.
Register the MCP Slack Python 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 MCP Slack Python. 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 MCP Slack Python MCP server (minji337/mcp-slack-python). 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 →