AI agents use users_set_photo 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.
This tool modifies user profile information (photo) but does not delete or destroy data, nor does it execute arbitrary code or move money. It's reversible (the photo can be changed again), making it Write rather than Destructive. Severity is medium because unauthorized photo changes could impact user identity/trust but have limited blast radius compared to destructive or financial actions.
From the tool's definition Tool name 'users_set_photo' indicates it sets/modifies a user's photo. The server description confirms it provides 'full access to Slack' with 220 tools. Setting a photo is a reversible modification of user profile data.
Attacks that exploit this kind of access
users_set_photo. 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_set_photo: 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_set_photo 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_set_photo 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_set_photo. 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_set_photo 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →