agents_traces_stats
Aggregated trace statistics for one agent over the last N days — total runs, success rate, avg duration, error breakdown, top tools used, runs-per-day histogram. Use this when you want a bird's-eye view of an agent's health before diving into individual traces with agents.traces_list / agents.tra...
This record as markdown: /tools/io-github-saloprj-dialogbrain/agents-traces-stats.md
What agents_traces_stats does on Dialogbrain
AI agents call agents_traces_stats 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 |
|---|---|---|---|
days | integer | — | Rolling window in days (1–30). |
agent_id | integer | Yes | Agent ID to compute stats for (must belong to your workspace). |
Parameters from the server's own tool schema.
Why agents_traces_stats is rated Low
This tool only queries and returns statistical summaries about agent performance over a time period. It performs no writes, executions, deletions, or financial operations. The read-only nature and analytics-focused purpose align squarely with the Read category. Low severity because unauthorized access to aggregated statistics poses minimal risk compared to operational tools.
From the tool's definition Tool retrieves aggregated trace statistics (total runs, success rate, avg duration, error breakdown, top tools used, runs-per-day histogram) with no modification or deletion of data.
Attacks that exploit this kind of access
The rule that runs agents_traces_stats 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 agents_traces_stats, this is the rule to start with:
agents_traces_stats 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 agents_traces_stats call is checked against it from then on.
Questions about agents_traces_stats
Aggregated trace statistics for one agent over the last N days — total runs, success rate, avg duration, error breakdown, top tools used, runs-per-day histogram. Use this when you want a bird's-eye view of an agent's health before diving into individual traces with agents.traces_list / agents.trace_get. Scoped to the target agent (exact match, no substring bleed). days is capped at 30 — matches the ClickHouse request_traces TTL. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
agents_traces_stats accepts 2 parameters: days, agent_id. Required: agent_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 agents_traces_stats: 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.
agents_traces_stats 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 agents_traces_stats 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 agents_traces_stats. 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.
agents_traces_stats 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