group_create
Create a new group on a channel (Telegram or WhatsApp). Returns the new group's chat ID and invite link. What this does: - Creates a new group with the specified title - Returns chat_id, invite_link, and channel_ref for further operations - Optionally registers the group in your inbox for monitor...
This record as markdown: /tools/io-github-saloprj-dialogbrain/group-create.md
What group_create does on Dialogbrain
AI agents use group_create to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
about | string | — | Optional description or about text for the group |
title | string | Yes | Title/name of the group to create |
channel | string | Yes | Channel to create the group on (e.g., 'telegram', 'whatsapp') |
group_type | string | — | Type of group to create. Options: 'supergroup' (default), 'basic'. Telegram-only; ignored on WhatsApp. |
register_in_inbox | boolean | — | Auto-register the created group in your inbox for monitoring. Default: true. |
Parameters from the server's own tool schema.
Why group_create is rated Medium
This tool creates a new group, which is a Write operation—it creates data (a new group resource) with reversible side effects. It does not execute arbitrary code, delete anything, move money, or cause irreversible damage. Creating a group is a standard communication action that can be undone by deleting the group later.
From the tool's definition Tool creates a new group on Telegram or WhatsApp with specified title, returning chat_id and invite_link. Description explicitly states 'Create a new group' with reversible creation of a new communication channel.
Attacks that exploit this kind of access
The rule that runs group_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For group_create, this is the rule to start with:
group_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every group_create call is checked against it from then on.
Questions about group_create
Create a new group on a channel (Telegram or WhatsApp). Returns the new group's chat ID and invite link. What this does: - Creates a new group with the specified title - Returns chat_id, invite_link, and channel_ref for further operations - Optionally registers the group in your inbox for monitoring Returns: success, chat_id, channel_ref, title, thread_id. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
group_create accepts 5 parameters: about, title, channel, group_type, register_in_inbox. Required: title, channel. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for group_create: 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 Dialogbrain. Nothing to install.
group_create 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 group_create 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 group_create. 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.
group_create is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue