group_scan
Scan a group to evaluate its quality before joining. Fetches recent messages, analyzes activity, spam, and engagement, then returns a quality score and plain-English verdict. When to use: - After finding groups with group.search - Before deciding which groups to join Returns: overall_score (0-1),...
This record as markdown: /tools/io-github-saloprj-dialogbrain/group-scan.md
What group_scan does on Dialogbrain
AI agents call group_scan 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 |
|---|---|---|---|
group_id | integer | Yes | ID of the discovered group (from group.search or group.list) |
Parameters from the server's own tool schema.
Why group_scan is rated Low
This tool retrieves and analyzes data from an existing group (messages, activity metrics, spam indicators, engagement levels) to generate an assessment score. It is purely informational with no side effects. The analysis happens on retrieved data, not on the group itself. This is a classic Read operation: query existing data to inform decision-making before an action (joining) that the user must then decide to take.
From the tool's definition Tool description states it 'Fetches recent messages, analyzes activity' and 'returns a quality score and plain-English verdict.' The key verbs are 'Scan,' 'Fetches,' and 'analyzes'—all read-only operations.
Attacks that exploit this kind of access
The rule that runs group_scan 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_scan, this is the rule to start with:
group_scan 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_scan call is checked against it from then on.
Questions about group_scan
Scan a group to evaluate its quality before joining. Fetches recent messages, analyzes activity, spam, and engagement, then returns a quality score and plain-English verdict. When to use: - After finding groups with group.search - Before deciding which groups to join Returns: overall_score (0-1), is_disqualified, disqualify_reasons, individual scores, and a verdict string. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
group_scan accepts 1 parameter: group_id. 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_scan: 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_scan 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_scan 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_scan. 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_scan 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