summarize_device_traffic

SERVERBusymate DevTools SOURCEhttps://mcp.busymate.dev

High RISK CLASS

Category Execute

Parameters 60 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-busymate-busymate-devtools/summarize-device-traffic.md

WHAT IT DOES

What summarize_device_traffic does on Busymate DevTools

AI agents invoke summarize_device_traffic to trigger actions in Busymate DevTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

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	—	The device's name — an alternative to device_uuid; one of the two is REQUIRED.
`device_uuid`	string	—	REQUIRED unless deviceName is given — the device to summarize.

Parameters from the server's own tool schema.

RISK

Why summarize_device_traffic is rated High

summarize_device_traffic triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Risk signalsAccepts URL/endpoint input (host)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

summarize_device_traffic stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "summarize_device_traffic": {
      "limits": [
        {
          "counter": "summarize_device_traffic_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about summarize_device_traffic

What does the summarize_device_traffic tool do? +

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. REQUIRES a device (device_uuid or deviceName) — a host alone is NOT enough: if you don't know which device, ask the user (or check list_devices) BEFORE calling. 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 Execute tool in the Busymate DevTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does summarize_device_traffic accept? +

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.

How do I enforce a policy on summarize_device_traffic? +

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.

What risk level is summarize_device_traffic? +

summarize_device_traffic is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit summarize_device_traffic? +

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.

How do I block summarize_device_traffic completely? +

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.

What MCP server provides summarize_device_traffic? +

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.

KEEP EXPLORING

More on Busymate DevTools, and thousands of servers like it.

This server

All 44 Busymate DevTools tools → High-risk tools on this server →

Across the catalogue

adb_backup_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →