Add a participant to a group chat.
AI agents use add_participant to create or update resources in Bluebubbles — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bluebubbles environment.
Adding a participant to a group chat creates a new association/relationship in the chat data structure. This is a write operation as it modifies existing data (the group's participant list) reversibly. The severity is medium because unauthorized addition could expose sensitive conversations to unintended parties and cause communication disruption, but the action is reversible (the participant can be removed).
From the tool's definition Tool description states 'Add a participant to a group chat', which modifies group membership by adding a member. This is a reversible modification (participants can be removed later).
Attacks that exploit this kind of access
Add a participant to a group chat. It is categorised as a Write tool in the Bluebubbles MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for add_participant: 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.
add_participant 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 add_participant 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 add_participant. 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.
add_participant 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 →