AI agents call slack_get_user_info to retrieve information from MCP 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 profile information from Slack without creating, modifying, deleting, or executing any operations. It is a straightforward read operation consistent with the read-only nature of the server. The blast radius of misuse is minimal—exposure of user metadata such as names, titles, or contact information is a data disclosure risk but not destructive or system-altering.
From the tool's definition Tool name 'slack_get_user_info' and description 'Get information about a Slack user' indicate a retrieval operation with no modification or side effects. Server description explicitly states 'Secure read-only MCP server for Slack workspaces'.
Attacks that exploit this kind of access
Get information about a Slack user. It is categorised as a Read tool in the MCP Slack MCP Server, which means it retrieves data without modifying state.
Register the MCP Slack MCP server in PolicyLayer and add a rule for slack_get_user_info: 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. Nothing to install.
slack_get_user_info 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_user_info 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_user_info. 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_user_info is provided by the MCP Slack MCP server (pypi:mcp-slack-crunchtools). 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 →