slack_get_user_profile

Get detailed profile information for a specific user

SERVERSlack SOURCE@modelcontextprotocol/server-slack

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/slack/slack-get-user-profile.md

WHAT IT DOES

What slack_get_user_profile does on Slack

AI agents call slack_get_user_profile to retrieve information from Slack without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why slack_get_user_profile is rated Low

This tool retrieves user profile data without side effects. It is a read-only query that does not modify state, execute code, or cause irreversible changes. The blast radius of misuse is minimal (information disclosure only), justifying low severity.

From the tool's definition Tool name is 'slack_get_user_profile' and description states 'Get detailed profile information for a specific user' — a pure retrieval operation with no modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs slack_get_user_profile safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For slack_get_user_profile, this is the rule to start with:

slack_get_user_profile Allowed

slack_get_user_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slack_get_user_profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every slack_get_user_profile call is checked against it from then on.

FAQ

Questions about slack_get_user_profile

What does the slack_get_user_profile tool do? +

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.

How do I enforce a policy on slack_get_user_profile? +

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.

What risk level is slack_get_user_profile? +

slack_get_user_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit slack_get_user_profile? +

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.

How do I block slack_get_user_profile completely? +

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.

What MCP server provides slack_get_user_profile? +

slack_get_user_profile is provided by the Slack MCP server (@modelcontextprotocol/server-slack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Slack, and thousands of servers like it.

This server

All 8 Slack tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →