Get a user's profile information.
AI agents call get_user_profile to retrieve information from Slack MCP Server 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 data from Slack without modifying, deleting, or executing any operations. It is a straightforward read operation similar to other sibling tools like 'get_user_info' and 'get_channel_info' on the same server. The blast radius of misuse is minimal—an agent could learn personal details about users, but cannot alter data or trigger external actions.
From the tool's definition Tool name 'get_user_profile' and description 'Get a user's profile information' indicate a retrieval operation with no side effects. The verb 'Get' and action 'profile information' are characteristic of read-only queries.
Attacks that exploit this kind of access
Get a user's profile information. It is categorised as a Read tool in the Slack MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for get_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 MCP Server. Nothing to install.
get_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 get_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 get_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.
get_user_profile is provided by the Slack MCP Server MCP server (software-engineer-mj/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 →