This record as markdown: /tools/karbassi-slack-mcp/users-profile-set.md
What users_profile_set does on Slack
AI agents use users_profile_set to create or update resources in Slack, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Why users_profile_set is rated Medium
This tool modifies user profile data, which is a reversible write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), or move money (not Financial). The severity is high because unauthorized profile modifications could affect user identity, visibility, and communications across an organization's Slack workspace, impacting multiple users and trust in the system. Confidence is 0.
From the tool's definition Tool name 'users_profile_set' indicates a user profile modification operation. The '_set' suffix denotes mutation/write capability.
Attacks that exploit this kind of access
The rule that runs users_profile_set 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_set, this is the rule to start with:
users_profile_set stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_set call is checked against it from then on.
Questions about users_profile_set
users_profile_set is a write tool on the Slack MCP server. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP server in PolicyLayer and add a rule for users_profile_set: 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_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the users_profile_set 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_set. 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_set 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