# slack_get_user_profile

Get detailed profile information for a specific user

Agent View of the PolicyLayer registry record for `slack_get_user_profile`. HTML page: https://policylayer.com/tools/slack/slack-get-user-profile

## Facts

- Tool: `slack_get_user_profile`
- Server: Slack (`@modelcontextprotocol/server-slack`) — https://policylayer.com/tools/slack.md
- Install: `npx -y @modelcontextprotocol/server-slack`
- Homepage: https://github.com/modelcontextprotocol/server-slack
- Risk category: Read (Low risk)
- Registry record: grade F, identity verified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "slack_get_user_profile",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Slack:

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

## Other tools on Slack (7)

- `slack_get_channel_history` — Read — https://policylayer.com/tools/slack/slack-get-channel-history.md
- `slack_get_thread_replies` — Read — https://policylayer.com/tools/slack/slack-get-thread-replies.md
- `slack_get_users` — Read — https://policylayer.com/tools/slack/slack-get-users.md
- `slack_list_channels` — Read — https://policylayer.com/tools/slack/slack-list-channels.md
- `slack_add_reaction` — Write — https://policylayer.com/tools/slack/slack-add-reaction.md
- `slack_post_message` — Write — https://policylayer.com/tools/slack/slack-post-message.md
- `slack_reply_to_thread` — Write — https://policylayer.com/tools/slack/slack-reply-to-thread.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=slack · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/slack