This record as markdown: /tools/karbassi-slack-mcp/users-profile-get-extras.md
What users_profile_get_extras does on Slack
AI agents call users_profile_get_extras 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.
Why users_profile_get_extras is rated Low
This tool appears to retrieve user profile data (a read operation with no side effects). However, the empty description creates uncertainty about what 'extras' encompasses—it could potentially include sensitive profile fields like email, phone, or custom fields. In a Slack context where user profiles may contain PII, unauthorized retrieval poses privacy risks, warranting medium severity despite the read-only nature.
From the tool's definition Tool name 'users_profile_get_extras' contains 'get' which indicates data retrieval. Tool description is empty, limiting ability to confirm exact scope. The 'users_profile' prefix suggests it retrieves user profile information from Slack.
Attacks that exploit this kind of access
The rule that runs users_profile_get_extras 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 users_profile_get_extras, this is the rule to start with:
users_profile_get_extras is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Slack, apply this rule, and every users_profile_get_extras call is checked against it from then on.
Questions about users_profile_get_extras
users_profile_get_extras is a read tool on the Slack MCP server. 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 users_profile_get_extras: 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.
users_profile_get_extras 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 users_profile_get_extras 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 users_profile_get_extras. 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.
users_profile_get_extras is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Slack, and thousands of servers like it.
This server
Across the catalogue