# get_circuit_status

Inspect the circuit-breaker state for each upstream host the MCP server has called. Shows whether requests are being fast-failed (state=open), probing (half-open), or flowing normally (closed).

Agent View of the PolicyLayer registry record for `get_circuit_status`. HTML page: https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/get-circuit-status

## Facts

- Tool: `get_circuit_status`
- Server: Max MCP Server (`digital-crew-technologies/max-mcp-server`) — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server.md
- Homepage: https://github.com/Digital-Crew-Technologies/max-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_circuit_status",
    "arguments": {}
  }
}
```

## Why get_circuit_status is rated Low

This tool retrieves diagnostic information about circuit-breaker health status for upstream hosts. It performs a read-only inspection that does not modify state, execute commands, delete data, or trigger financial transactions. The blast radius of misuse is minimal—an agent cannot cause harm by repeatedly calling this diagnostic query. Classification: Read.

From the tool's own definition: "The tool 'inspect[s] the circuit-breaker state' and 'shows whether requests are being fast-failed...probing...or flowing normally'. These are observation and query operations with no side effects."

## Use case

AI agents call get_circuit_status to retrieve information from Max MCP Server 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 Max MCP Server:

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

## Other tools on Max MCP Server (414)

- `automation_cancel_run` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-cancel-run.md
- `automation_delete` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-delete.md
- `automation_discard_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/automation-discard-draft.md
- `bulk_delete_organizations` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-organizations.md
- `bulk_delete_prospects` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/bulk-delete-prospects.md
- `cancel_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting.md
- `cancel_meeting_series` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-meeting-series.md
- `cancel_warmup` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/cancel-warmup.md
- `clear_failed_requests` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/clear-failed-requests.md
- `decline_meeting` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/decline-meeting.md
- `delete_calendar_event` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-calendar-event.md
- `delete_campaign` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign.md
- `delete_campaign_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-campaign-attachment.md
- `delete_deal` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal.md
- `delete_deal_attachment` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-attachment.md
- `delete_deal_pipeline` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-pipeline.md
- `delete_deal_stage` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage.md
- `delete_deal_stage_rule` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-deal-stage-rule.md
- `delete_icp` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-icp.md
- `delete_meeting_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-meeting-link.md
- `delete_organization` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-organization.md
- `delete_prospect` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect.md
- `delete_prospect_list` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-list.md
- `delete_prospect_profile_hook` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-prospect-profile-hook.md
- `delete_saved_view` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-saved-view.md
- `delete_schedule_preset` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/delete-schedule-preset.md
- `disconnect_data_supplier` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/disconnect-data-supplier.md
- `pipeline_delete_campaign_route` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-campaign-route.md
- `pipeline_delete_canvas_draft` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-canvas-draft.md
- `pipeline_delete_link` — Destructive — https://policylayer.com/tools/digital-crew-technologies-max-mcp-server/pipeline-delete-link.md
- …and 384 more: https://policylayer.com/tools/digital-crew-technologies-max-mcp-server.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=digital-crew-technologies-max-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/digital-crew-technologies-max-mcp-server