group_list
List groups in this workspace's DISCOVERY/SCORING list (the discovered_group table). ⚠️ This is NOT your messageable inbox. It is a subset used for discovery + quality scoring, and its channel_ref may be un-normalized (raw positive id) and will NOT match a thread's channel_ref. Absence here does ...
This record as markdown: /tools/io-github-saloprj-dialogbrain/group-list.md
What group_list does on Dialogbrain
AI agents call group_list to retrieve information from Dialogbrain without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum number of results (1-100, default 20) |
offset | integer | — | Pagination offset. OMIT to start at row 0 (default). |
channel | string | — | Filter by channel (e.g. 'telegram'). Optional. |
lifecycle | string | — | Filter by state: discovered, bookmarked, monitored (=joined/syncing), dismissed. OMIT to include all states (dismissed excluded by default elsewhere). |
min_score | number | — | Minimum overall score (0.0-1.0). Optional. |
Parameters from the server's own tool schema.
Why group_list is rated Low
This tool retrieves and queries group information from a discovery/scoring database without any capability to create, modify, delete, or execute actions. It is purely informational.
From the tool's definition Tool name is 'group_list' and description states it 'List groups in this workspace's DISCOVERY/SCORING list'. The verb 'list' and the explicit purpose of retrieving/querying group metadata with no modification capability indicates a read-only operation.
Attacks that exploit this kind of access
The rule that runs group_list 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_list, this is the rule to start with:
group_list is read-only, so it stays allowed. 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_list call is checked against it from then on.
Questions about group_list
List groups in this workspace's DISCOVERY/SCORING list (the discovered_group table). ⚠️ This is NOT your messageable inbox. It is a subset used for discovery + quality scoring, and its channel_ref may be un-normalized (raw positive id) and will NOT match a thread's channel_ref. Absence here does NOT mean a chat isn't joined or can't be messaged. To find a chat you can actually send to (and get its thread_id), use search_threads — never rely on group.list for reachability. Lifecycle values: - discovered: found but not yet evaluated - bookmarked: saved for later - monitored: joined and actively syncing messages - dismissed: hidden By default, dismissed groups are excluded. Returns: id, title, member_count, lifecycle, scan_status, overall_score. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
group_list accepts 5 parameters: limit, offset, channel, lifecycle, min_score. 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_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the group_list 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_list. 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_list 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