group_join
Join a group and start syncing its messages to your inbox. The group must be in your discovery list (use group.search or group.add first). What this does: - Joins the group on Telegram (or other channel) - Creates a thread in your inbox for syncing messages - Optionally enables AI auto-reply draf...
This record as markdown: /tools/io-github-saloprj-dialogbrain/group-join.md
What group_join does on Dialogbrain
AI agents use group_join 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 |
|---|---|---|---|
group_id | integer | Yes | ID of the discovered group (from group.search or group.list) |
enable_auto_reply | boolean | — | Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: true. |
Parameters from the server's own tool schema.
Why group_join is rated Medium
This tool joins a group on an external platform and creates a new inbox thread — both are reversible write operations (you can leave a group or delete a thread). It does not delete data, execute arbitrary code, or move money. The medium severity reflects that joining groups on behalf of a user has meaningful social/account implications (e.g., joining unwanted or malicious groups), but the action is reversible.
From the tool's definition 'Joins the group on Telegram (or other channel)', 'Creates a thread in your inbox for syncing messages', 'Optionally enables AI auto-reply drafts'
Attacks that exploit this kind of access
The rule that runs group_join 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_join, this is the rule to start with:
group_join 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_join call is checked against it from then on.
Questions about group_join
Join a group and start syncing its messages to your inbox. The group must be in your discovery list (use group.search or group.add first). What this does: - Joins the group on Telegram (or other channel) - Creates a thread in your inbox for syncing messages - Optionally enables AI auto-reply drafts Returns: success, thread_id, auto_reply_enabled. 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_join accepts 2 parameters: group_id, enable_auto_reply. Required: group_id. 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_join: 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_join 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_join 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_join. 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_join 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