group_add
Add a specific group to your discovery list by @username or invite link (t.me/...). Groups and channels only — this does NOT add an individual person/contact. To add a person by @username (e.g. a customer or lead), use contacts.discover then contacts.sync instead. When to use: - You already know ...
This record as markdown: /tools/io-github-saloprj-dialogbrain/group-add.md
What group_add does on Dialogbrain
AI agents use group_add 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 |
|---|---|---|---|
link | string | Yes | The group's @username or invite link (e.g. '@phuket' or 't.me/...') |
channel | string | Yes | Channel the group is on (e.g. 'telegram') |
Parameters from the server's own tool schema.
Why group_add is rated Medium
This tool creates a new entry in the user's discovery list by adding a group. While it does not delete or irreversibly destroy data, it does modify the system state by expanding the set of groups under surveillance/management. This is a Write operation (reversible modification).
From the tool's definition The tool description states 'Add a specific group to your discovery list' — this is a create/add operation that modifies the user's list of monitored groups.
Attacks that exploit this kind of access
The rule that runs group_add 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_add, this is the rule to start with:
group_add 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_add call is checked against it from then on.
Questions about group_add
Add a specific group to your discovery list by @username or invite link (t.me/...). Groups and channels only — this does NOT add an individual person/contact. To add a person by @username (e.g. a customer or lead), use contacts.discover then contacts.sync instead. When to use: - You already know the group's @username or invite link - Adding a known group without searching Returns: group metadata including id, title, member_count. 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_add accepts 2 parameters: link, channel. Required: link, 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_add: 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_add 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_add 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_add. 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_add 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