// SCAN REPORT

BugEzy

13 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 5 Aug 2026

0 can modify or destroy data

13 read-only

13 tools total

Community server · catalogue entry checked 05/08/2026 · full schemas captured for 12 of 13 tools

How to control BugEzy ↓

TOOL MAP

What BugEzy exposes to your agents

Read (13) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What BugEzy costs in tokens

1,280 tokens of tool definitions, loaded on every request

0.6% of a 200k context window

165 heaviest tool: get_terminal_logs

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

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control BugEzy

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

Cap read operations

{
  "get_console_logs": {
    "limits": [
      {
        "counter": "get_console_logs_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 BugEzy — 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 BUGEZY →

Instant setup, no code required.

FULL CATALOGUE

All 13 BugEzy tools

READ 13 tools

Read get_console_logs 取得 Console 記錄（warn/error）。Console logs. Read get_live_errors 取得某使用者當前頁面的即時 Console/Network 錯誤（需 user_email + session_token 驗證身分）。Live console/network errors — requires use Read get_network_errors 取得 Network 錯誤（4xx/5xx）。Network errors. Read get_page_info 取得頁面資訊（URL/標題/瀏覽器/解析度）。Page info. Read get_report_overview 取得報告概覽（metadata + 各筆數 + AI Bug 導航摘要，不含原始資料）。Report overview with AI bug summary. Read get_rrweb_events 取得完整 DOM 事件（⚠ 資料量大）。Full rrweb events. Read get_rrweb_summary DOM 軌跡摘要（事件數/時長/類型分布，不回完整資料）。rrweb summary. Read get_screenshots 高畫質 AI 分析：取得報告截圖圖片（視覺 Bug 用）。⚠ 圖片消耗較高 Token（每張 ~3,000-8,000），建議只在需要看畫面時使用。Report screenshots. Read get_terminal_logs 取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command> Read get_timeline 取得一份報告的完整時間軸（時序麵包屑）。把 Console、Network、語音、標記、網路環境、儲存狀態全部按時間排序成一條故事線，AI 只需呼叫這一個 tool 就能掌握完整 Bug 脈絡（省去逐一呼叫 consol Read get_usage_stats 取得當月的 MCP 使用量統計（呼叫次數、token 消耗、省了多少）。Monthly MCP usage stats. Read get_voice_transcript 取得開發者語音描述（中文轉錄）。Developer voice transcript. Read list_reports 列出某使用者的 Bug 報告（需提供 user_email + session_token 驗證身分）。List a user's bug reports — requires user_email and sessio

FAQ

Questions about BugEzy

Is the BugEzy MCP server safe to use without restrictions? +

The BugEzy server is primarily read-only with 13 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 BugEzy MCP server expose? +

13 tools across 1 categories: Read. 13 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on BugEzy? +

Register the BugEzy 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 BugEzy tool call.

Deterministic rules across all 13 BugEzy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BUGEZY →

Instant setup, no code required.

13 BugEzy tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from BugEzy'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 →