Remove a custom emoji (undocumented session endpoint).
AI agents call emoji_remove 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 deletes custom emoji from a Slack workspace, which is an irreversible operation that cannot be undone through normal means. While the blast radius is limited to emoji assets (not critical business data), the destructive nature of deletion operations places it in the Destructive category. An AI agent could maliciously remove organizational emoji branding or symbols.
From the tool's definition Tool name 'emoji_remove' combined with description stating it removes a custom emoji. The verb 'remove' indicates irreversible deletion of a workspace asset.
Attacks that exploit this kind of access
Remove a custom emoji (undocumented session endpoint). 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 emoji_remove: 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.
emoji_remove 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 emoji_remove 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 emoji_remove. 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.
emoji_remove 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 →