Resolve a user by email or display name.
AI agents call slack_find_user to retrieve information from Work Integrations MCP 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 Slack based on search criteria (email or display name). It performs a read-only query with no side effects, data modification, or external operations triggered. The blast radius of misuse is minimal—an agent could only discover user identities, not modify data or access sensitive content beyond what the integration already permits.
From the tool's definition Tool name 'slack_find_user' and description 'Resolve a user by email or display name' indicate a lookup/query operation with no modification of data.
Attacks that exploit this kind of access
Resolve a user by email or display name. It is categorised as a Read tool in the Work Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Work Integrations MCP server in PolicyLayer and add a rule for slack_find_user: 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 Work Integrations MCP. Nothing to install.
slack_find_user 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_find_user 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_find_user. 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_find_user is provided by the Work Integrations MCP server (nazarky/workspace-mcp). 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 →