create_chat
AI agents use create_chat 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.
Creating a new chat is a write operation that modifies the message database state by adding new conversation records. It is reversible (chats can be deleted via delete_chat sibling tool), so it does not qualify as Destructive.
From the tool's definition Tool name 'create_chat' combined with server description stating it 'support[s] comprehensive chat management features' including the ability to 'send messages' and related write operations (edit_message, delete_message present as siblings).
Attacks that exploit this kind of access
create_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 create_chat: 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.
create_chat 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 create_chat 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 create_chat. 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.
create_chat 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 →