rename_group · Bluebubbles MCP: Risk & Policy

WHAT IT DOES

What rename_group does on Bluebubbles

AI agents use rename_group 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.

WHY IT NEEDS A POLICY

Why rename_group needs a policy

Renaming a group chat modifies chat properties but does not delete data or execute arbitrary code. It is reversible (can be renamed again), so it falls under Write rather than Destructive. The severity is medium because misuse could cause confusion or disruption in group communications, but the impact is limited to metadata and affects only that specific chat's name.

From the tool's definition Tool name 'rename_group' and description 'Rename a group chat' indicate modification of existing group chat metadata. This is a reversible data mutation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_group Rate-limited

rename_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rename_group": {
      "limits": [
        {
          "counter": "rename_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bluebubbles, so you can run agents against it safely.

FAQ

Questions about rename_group

What does the rename_group tool do? +

Rename 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.

How do I enforce a policy on rename_group? +

Register the Bluebubbles MCP server in PolicyLayer and add a rule for rename_group: 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.

What risk level is rename_group? +

rename_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rename_group? +

Yes. Add a rate_limit block to the rename_group 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.

How do I block rename_group completely? +

Set action: deny in the PolicyLayer policy for rename_group. 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.

What MCP server provides rename_group? +

rename_group 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.