Remove a group chat's icon.
AI agents call remove_group_icon to permanently remove resources in Bluebubbles — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a group chat icon is an irreversible deletion of the chat's icon/image. There is no indication of an undo mechanism, making this a destructive action that permanently removes the group icon.
From the tool's definition Remove a group chat's icon
Attacks that exploit this kind of access
Remove a group chat's icon. It is categorised as a Destructive tool in the Bluebubbles MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for remove_group_icon: 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 Bluebubbles. Nothing to install.
remove_group_icon 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 remove_group_icon 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 remove_group_icon. 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.
remove_group_icon is provided by the Bluebubbles MCP server (metaember/bluebubbles-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 →