summarize_device_traffic
BOUNDED traffic aggregation for ONE device — the FIRST tool to call to report what a device is doing, find the busy/flooding host, or pick a host to clean up. NEVER scans or returns raw rows (use it instead of search_entries/inspect_requests on a high-volume device — those time out at scale). Omi...
This record as markdown: /tools/dev-busymate-busymate-devtools/summarize-device-traffic.md
What summarize_device_traffic does on Busymate DevTools
AI agents call summarize_device_traffic to retrieve information from Busymate DevTools 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 |
|---|---|---|---|
host | string | — | Omit for top hosts; pass a full hostname to get its top path-bases. |
after | string | — | Only entries with ts >= this ISO date/datetime. |
limit | number | — | Max groups (default 25, capped 100). |
before | string | — | Only entries with ts < this ISO date/datetime. |
deviceName | string | — | |
device_uuid | string | — |
Parameters from the server's own tool schema.
Why summarize_device_traffic is rated Low
This tool performs read-only aggregation and summarization of traffic data for a single device. It explicitly states it returns only metadata (host, path_base, count, last_seen) with no request/response content, making it a bounded, non-destructive read operation. The blast radius of misuse is low since it only exposes traffic statistics, not sensitive payload data.
From the tool's definition 'BOUNDED traffic aggregation', 'no headers/bodies', 'Returns ONLY {host|path_base, count, last_seen}', 'NEVER scans or returns raw rows'
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs summarize_device_traffic safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Busymate DevTools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For summarize_device_traffic, this is the rule to start with:
summarize_device_traffic 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 Busymate DevTools, apply this rule, and every summarize_device_traffic call is checked against it from then on.
Questions about summarize_device_traffic
BOUNDED traffic aggregation for ONE device — the FIRST tool to call to report what a device is doing, find the busy/flooding host, or pick a host to clean up. NEVER scans or returns raw rows (use it instead of search_entries/inspect_requests on a high-volume device — those time out at scale). Omit host → top hosts by request count (which host dominates). Pass host → top path-bases on that host with per-path count + last-seen (which endpoint floods). Optional absolute time range. Fast on 17k+ rows (one index-only GROUP BY). Returns ONLY {host|path_base, count, last_seen} — no headers/bodies. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
summarize_device_traffic accepts 6 parameters: host, after, limit, before, deviceName, device_uuid. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools MCP server in PolicyLayer and add a rule for summarize_device_traffic: 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 Busymate DevTools. Nothing to install.
summarize_device_traffic 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 summarize_device_traffic 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 summarize_device_traffic. 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.
summarize_device_traffic is provided by the Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue