This record as markdown: /tools/karbassi-slack-mcp/users-prefs-get.md
What users_prefs_get does on Slack
AI agents call users_prefs_get 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_prefs_get is rated Low
This tool retrieves user preferences without modifying or deleting data. However, user preferences may contain sensitive personal configuration data (notification settings, display preferences, etc.), warranting medium severity due to potential privacy exposure if misused by an AI agent to extract user-specific information from multiple accounts.
From the tool's definition Tool name 'users_prefs_get' and description 'Get user preferences' indicate data retrieval with no modification. The term 'get' is explicitly a Read operation per the classification rules.
Attacks that exploit this kind of access
The rule that runs users_prefs_get 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_prefs_get, this is the rule to start with:
users_prefs_get 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_prefs_get call is checked against it from then on.
Questions about users_prefs_get
Get user preferences (legacy undocumented). 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_prefs_get: 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_prefs_get 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_prefs_get 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_prefs_get. 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_prefs_get 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