# get_network_errors

取得 Network 錯誤（4xx/5xx）。Network errors.

Agent View of the PolicyLayer registry record for `get_network_errors`. HTML page: https://policylayer.com/tools/dev-bugezy-bugezy/get-network-errors

## Facts

- Tool: `get_network_errors`
- Server: BugEzy (`https://bugezy.dev/mcp`) — https://policylayer.com/tools/dev-bugezy-bugezy.md
- Homepage: https://github.com/fox100039-design/bugezy
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `report_id` | string | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_network_errors",
    "arguments": {
      "report_id": "<report_id>"
    }
  }
}
```

## Why get_network_errors is rated Low

Even though get_network_errors only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call get_network_errors to retrieve information from BugEzy without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches BugEzy:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_network_errors": {}
  }
}
```

## Other tools on BugEzy (12)

- `get_console_logs` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-console-logs.md
- `get_live_errors` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-live-errors.md
- `get_page_info` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-page-info.md
- `get_report_overview` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-report-overview.md
- `get_rrweb_events` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-rrweb-events.md
- `get_rrweb_summary` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-rrweb-summary.md
- `get_screenshots` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-screenshots.md
- `get_terminal_logs` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-terminal-logs.md
- `get_timeline` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-timeline.md
- `get_usage_stats` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-usage-stats.md
- `get_voice_transcript` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/get-voice-transcript.md
- `list_reports` — Read — https://policylayer.com/tools/dev-bugezy-bugezy/list-reports.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-bugezy-bugezy · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-bugezy-bugezy