Read user info/profile using users.info plus users.profile.get (best effort).
AI agents call read_user_profile to retrieve information from Slack Max API 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 profile information from Slack without creating, modifying, or deleting any data. It is a straightforward query operation with no side effects. The blast radius of misuse is low—an agent could exfiltrate user profile data but cannot modify workspaces, trigger actions, or cause irreversible harm.
From the tool's definition Tool name contains 'read' and description states 'Read user info/profile' using read-only API methods (users.info and users.profile.get). No modification, deletion, or external execution occurs.
Attacks that exploit this kind of access
Read user info/profile using users.info plus users.profile.get (best effort). It is categorised as a Read tool in the Slack Max API MCP MCP Server, which means it retrieves data without modifying state.
Register the Slack Max API MCP server in PolicyLayer and add a rule for read_user_profile: 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 Max API MCP. Nothing to install.
read_user_profile 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 read_user_profile 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 read_user_profile. 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.
read_user_profile is provided by the Slack Max API MCP server (jeongwoobin335/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 →