Delete the user profile photo.
AI agents call users_delete_photo to permanently remove resources in Slack — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a user's profile photo, which cannot be undone without re-uploading. Deletion operations are classified as Destructive. Severity is high because an AI agent could maliciously delete profile photos of multiple users, affecting their account presentation and user experience across the organization, though the blast radius is limited to cosmetic/profile metadata rather than critical…
From the tool's definition Tool name 'users_delete_photo' and description 'Delete the user profile photo' explicitly perform an irreversible deletion operation on user profile data.
Attacks that exploit this kind of access
Delete the user profile photo. It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for users_delete_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_delete_photo is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the users_delete_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_delete_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_delete_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 →