// SCAN REPORT

Busymate DevTools

44 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 18 Aug 2026

2 can modify or destroy data

42 read-only

44 tools total

Community server · catalogue entry checked 18/08/2026 · full schemas captured for 37 of 44 tools

How to control Busymate DevTools ↓

TOOL MAP

What Busymate DevTools exposes to your agents

Read (42) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Busymate DevTools costs in tokens

13,115 tokens of tool definitions, loaded on every request

6.6% of a 200k context window

1,939 heaviest tool: list_device_events

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Busymate DevTools tools

Execute · High share_advisor_finding Build a SHAREABLE package for ONE advisor finding — the max-context markdown + flat LLM prose + the permalink, so it can be dropped into a d Execute · Medium 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

2 of Busymate DevTools's 44 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Busymate DevTools

PolicyLayer is an MCP gateway — it sits between your AI agents and Busymate DevTools, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "download_snapshot": {
    "limits": [
      {
        "counter": "download_snapshot_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Busymate DevTools — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON BUSYMATE DEVTOOLS →

Instant setup, no code required.

FULL CATALOGUE

All 44 Busymate DevTools tools

EXECUTE 2 tools

Execute share_advisor_finding Build a SHAREABLE package for ONE advisor finding — the max-context markdown + flat LLM prose + the permalink, Execute summarize_device_traffic BOUNDED traffic aggregation for ONE device — the FIRST tool to call to report what a device is doing, find the

READ 42 tools

Read download_snapshot Get a 5-minute signed download URL for a snapshot file (name from list_snapshots). Read export_har Export captured entries as a HAR 1.2 log. Optionally scope by device, host, and date range. Read get_advisor_finding Get ONE advisor finding in FULL by its fingerprint (from list_advisor_findings) — with its up-to-20 resolved ( Read get_audit_event Get ONE audit-trail row in FULL by its id (from list_audit_events) — including the fields the list omits: the Read get_block_rules_device Read what ONE device ENFORCES — the EFFECTIVE 4-tier block-rule union (global ++ service ++ user ++ device, de Read get_device Get one device row by uuid, name, OR its PAC PORT — the DIRECT resolver for a KNOWN device: when you already h Read get_device_egress_fail_posture Read a device's PAC egress FAIL POSTURE (1657) — what the proxy does when the device is handed the 76 PAC DIRE Read get_device_egress_status Read a device's egress-IP set (1432) — the device→proxy INGRESS / CONNECT-source ADMISSION IPs the proxy allow Read get_device_health THE ONE QUERY (1157/1160): the latest capture-health projection for ONE device — one device_health row, no sca Read get_device_settings Read settings_device for one device (device_uuid or deviceName). Read get_device_status Get a device's live status: online is DERIVED truth (776 — devices.last_seen_at within 90s, 150s for farm host Read get_entry Get ONE captured entry's FULL detail by the id you already hold — method, URL, host, path, status, timing (dur Read get_entry_count Count entries in a workspace (workspace_id or workspace_slug) with optional device/host/method/status/search f Read get_my_account YOUR account at a glance — ONE self-scoped read returning the calling account's profile (name, display_name, e Read get_push_response Read back a device's answer to an actionable push (75) by the correlation_id returned from send_push. Returns Read get_service_group Get one service group by id or name. Read get_stats Return the live stats snapshot (get_stats RPC). Read get_status Return the latest infra status snapshot (service_status) MERGED with the Edge tier's self-reported deployed bu Read get_subscription Return the caller's OWN Stripe subscription(s) — status/price/product/quantity/period/trial/cancel-at-period-e Read get_todo Get ONE of YOUR to-dos by id — its full row. Owner-scoped: an id you don't own returns not-found (never reveal Read get_usage Return the caller's OWN metered usage rollup (metric captured_entries = count of captured entries per device p Read get_workspace Get one workspace by id or slug. Read inspect_requests Deep-inspect FULL captured request/response detail for ONE host — method, URL, request + response HEADERS, and Read list_advisor_findings Browse the ADVISOR CENTER findings (public.advisor_findings) — the advisor-monitor's deduped audit/health find Read list_audit_events Read the platform AUDIT TRAIL (public.audit_log) — the unified who-did-what-when-how ledger across every surfa Read list_breakpoint_events List HELD (paused) breakpoint exchanges — the READ side of the breakpoint-continue flow (public.breakpoint_eve Read list_device_audit_modes Every device with AUDIT-mode telemetry currently armed — device_uuid + name, enabled, expires_at + expires_in, Read list_device_events The MULTI-PRODUCER device TELEMETRY event stream (1160/1208) — every DECISION and STATE TRANSITION reported ab Read list_device_service_groups List the device↔service-group membership edges (public.device_service_groups) — the delegation boundary: which Read list_devices List devices, ONE PAGE at a time — YOUR OWN by default (owner-scoped to the calling account: the same reach th Read list_entries LIST the newest captured traffic entries as SLIM feed rows (id, ts, device, kind, request_id, host, path, meth Read list_invoices List the caller's OWN Stripe invoices — status/amounts (minor units)/currency/hosted_invoice_url/period (from Read list_issue_reports List issue reports from the one-tap reporter (public.issue_reports — the durable rows behind report_issue + th Read list_push_tokens List registered device push tokens (masked), PLATFORM-ROUTED (1542): each device_push_tokens row carries a pla Read list_service_groups List every service group (full rows incl. ssl_proxy_domains) with each group's primary_agent + ordered agents[ Read list_snapshots List snapshot files in the snapshots storage bucket. Read list_tabs List a workspace's tabs (workspace_id or workspace_slug). Read list_todos List YOUR to-dos from the /todo app (public.todos) — the shared "what to do / what's done" list you + the user Read list_workspaces List workspaces. YOUR OWN by default (owner-scoped to the caller — the reach the dashboard RLS owner arm gives Read search_entries LOCATE captured entries by ANY keyword q — matched against the host/url/path AND the DECRYPTED request/respons Read test_pac_connection PROVE whether PAC capture actually works for ONE device — the "is it really working?" answer, not "does it loo

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Busymate DevTools

Is the Busymate DevTools MCP server safe to use without restrictions? +

The Busymate DevTools server is primarily read-only with 42 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Busymate DevTools MCP server expose? +

44 tools across 3 categories: Execute, Read, Write. 42 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Busymate DevTools? +

Register the Busymate DevTools MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Busymate DevTools tool call.

Deterministic rules across all 44 Busymate DevTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BUSYMATE DEVTOOLS →

Instant setup, no code required.

44 Busymate DevTools tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Busymate DevTools's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →