analytics_query
Answer analytics questions about this workspace's own data (conversations, messages, voice calls) — e.g. 'how many new conversations this week by channel' or 'inbound vs outbound messages per day this month'. Returns rows plus a chart hint. Read-only and scoped to the current workspace.
This record as markdown: /tools/io-github-saloprj-dialogbrain/analytics-query.md
What analytics_query does on Dialogbrain
AI agents call analytics_query 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 |
|---|---|---|---|
question | string | Yes | The analytics question in natural language, e.g. 'how many conversations started this week, by channel?' |
Parameters from the server's own tool schema.
Why analytics_query is rated Low
This tool retrieves and queries workspace analytics data with no side effects. It aggregates historical conversation, message, and call information to answer analytical questions. The explicit 'read-only' designation and scoping to current workspace confirm it poses minimal risk—it neither modifies data, executes external operations, nor affects financial systems.
From the tool's definition Tool description explicitly states 'Read-only and scoped to the current workspace' and provides examples of analytics queries (conversation counts, message statistics, call data) that retrieve and aggregate existing data without modification.
Attacks that exploit this kind of access
The rule that runs analytics_query 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 analytics_query, this is the rule to start with:
analytics_query 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 analytics_query call is checked against it from then on.
Questions about analytics_query
Answer analytics questions about this workspace's own data (conversations, messages, voice calls) — e.g. 'how many new conversations this week by channel' or 'inbound vs outbound messages per day this month'. Returns rows plus a chart hint. Read-only and scoped to the current workspace. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
analytics_query accepts 1 parameter: question. Required: question. 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 analytics_query: 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.
analytics_query 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 analytics_query 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 analytics_query. 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.
analytics_query 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