AI agents call users_identity 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 tool retrieves user identity data without creating, modifying, deleting, or executing any operations. It falls clearly into the Read category as it only queries and returns information. The severity is low because user identity information, while sensitive, is not typically mission-critical and disclosure does not directly compromise system integrity or financial assets in most contexts.
From the tool's definition Tool name 'users_identity' and description 'Get a user's identity' indicate data retrieval with no modification or side effects. This is a straightforward query operation that fetches user identity information.
Attacks that exploit this kind of access
Get a user's identity. 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 users_identity: 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.
users_identity 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 users_identity 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 users_identity. 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.
users_identity is provided by the Slack MCP server (karbassi/slack-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 →