List all known participants across indexed Slack threads.
AI agents call list_users to retrieve information from Slack Indexed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation that enumerates users from indexed data. It has no side effects, cannot modify data, execute code, or cause financial impact. The blast radius of misuse is minimal—exposing a list of known Slack participants is low-risk information disclosure. Severity is low because user lists are typically non-sensitive metadata in most organizational contexts.
From the tool's definition Tool name 'list_users' and description 'List all known participants across indexed Slack threads' indicate retrieval of user information without modification or execution of code. This is a query operation that reads data from the Slack index.
Attacks that exploit this kind of access
List all known participants across indexed Slack threads. It is categorised as a Read tool in the Slack Indexed MCP Server, which means it retrieves data without modifying state.
Register the Slack Indexed MCP server in PolicyLayer and add a rule for list_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 Indexed. Nothing to install.
list_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 list_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 list_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.
list_users is provided by the Slack Indexed MCP server (kanvabhatia-alaan/alaan-slack-indexed-mcp-tool). 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 →