Get detailed profile information for a specific user
AI agents call slack_get_user_profile 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 queries and retrieves user profile data from Slack. It performs no modification, deletion, execution, or financial action. The 'get' verb and 'profile information' retrieval confirm this is a read-only operation.
From the tool's definition Tool name 'slack_get_user_profile' and description 'Get detailed profile information for a specific user' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access slack_get_user_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Slack, and nothing reaches the server without passing your rules. This is the rule we recommend for slack_get_user_profile:
{
"version": "1",
"default": "deny",
"tools": {
"slack_get_user_profile": {}
}
}slack_get_user_profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed profile information for a specific user. 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 slack_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. Nothing to install.
slack_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 slack_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 slack_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.
slack_get_user_profile is provided by the Slack MCP server (zencoderai/slack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Slack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Slack tools catalogued and risk-classified — across an index of 42,500+ MCP servers.