# singularityagent__chain_liveness Check that a chain is actually producing blocks, rather than merely answering. A chain that has halted still responds to every request, with the correct chain id, serving the last block it ever made — so a balance read from it is historical state carrying no indication that it is historical. Each configured endpoint is probed separately, so this also reports endpoints that answer but lag behind the others, and chains left with no working failover. Call it when a read looks implausible, when an answer must be current to be worth acting on, or before treating an absence as fact. status is one of: live; stale (the head is old enough that nothing here is current); lagging (endpoints disagree enough that which one answers changes the result); single (only one endpoint answered, so the next failure is total); undatable (answering, but nothing will say when the head was produced); skewed (the head is dated in the future, so its age proves nothing); down. Only live means the chain can be read with confidence, and stale in particular does not surface as an error anywhere else. Agent View of the PolicyLayer registry record for `singularityagent__chain_liveness`. HTML page: https://policylayer.com/tools/ai-rokha-rokha/singularityagent--chain-liveness ## Facts - Tool: `singularityagent__chain_liveness` - Server: Rokha (`https://rokha.ai/mcp/jsonrpc`) — https://policylayer.com/tools/ai-rokha-rokha.md - Homepage: https://github.com/aetherBytes/rokha-sdk - Risk category: Read (Low risk) - Registry record: grade F, identity unverified - Server auth posture: open - Server rate-limited: no - Parameters: 1 - Recommended policy verdict: Allowed ## Parameters | Parameter | Type | Required | Description | | --- | --- | --- | --- | | `chain` | array | no | Chain ids or aliases to check. Defaults to every configured chain. | 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": "singularityagent__chain_liveness", "arguments": {} } } ``` ## Why singularityagent__chain_liveness is rated Low Tool queries blockchain liveness status without modifying data or triggering external operations. From the tool's own definition: "Check that a chain is actually producing blocks, probes endpoints separately" Risk signals: Bulk/mass operation — affects multiple targets ## Use case AI agents call singularityagent__chain_liveness to retrieve information from Rokha 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 Rokha: ```json { "version": "1", "default": "deny", "tools": { "singularityagent__chain_liveness": {} } } ``` ## Other tools on Rokha (215) - `adspace_bid_cancel` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid-cancel.md - `delete_harness` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/delete-harness.md - `hook_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/hook-delete.md - `rig_node_remove` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/rig-node-remove.md - `schedule_delete` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/schedule-delete.md - `signet_paper_reset` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-paper-reset.md - `signet_revoke` — Destructive — https://policylayer.com/tools/ai-rokha-rokha/signet-revoke.md - `auth_wallet_verify` — Execute — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-verify.md - `harness_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/harness-author.md - `orbitx__orbitx_gc_focus` — Execute — https://policylayer.com/tools/ai-rokha-rokha/orbitx--orbitx-gc-focus.md - `registry_adopt` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-adopt.md - `registry_list_server` — Execute — https://policylayer.com/tools/ai-rokha-rokha/registry-list-server.md - `rig_author` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-author.md - `rig_run` — Execute — https://policylayer.com/tools/ai-rokha-rokha/rig-run.md - `sandbox_exec` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-exec.md - `sandbox_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-start.md - `sandbox_stop` — Execute — https://policylayer.com/tools/ai-rokha-rokha/sandbox-stop.md - `send_agent_message` — Execute — https://policylayer.com/tools/ai-rokha-rokha/send-agent-message.md - `signet_approve` — Execute — https://policylayer.com/tools/ai-rokha-rokha/signet-approve.md - `singularityagent__mesh` — Execute — https://policylayer.com/tools/ai-rokha-rokha/singularityagent--mesh.md - `studio_doors` — Execute — https://policylayer.com/tools/ai-rokha-rokha/studio-doors.md - `x_link_start` — Execute — https://policylayer.com/tools/ai-rokha-rokha/x-link-start.md - `adnet_feed` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-feed.md - `adnet_join` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adnet-join.md - `ads_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/ads-order.md - `adspace_bid` — Financial — https://policylayer.com/tools/ai-rokha-rokha/adspace-bid.md - `auth_wallet_challenge` — Financial — https://policylayer.com/tools/ai-rokha-rokha/auth-wallet-challenge.md - `campaign_claim` — Financial — https://policylayer.com/tools/ai-rokha-rokha/campaign-claim.md - `carry_order` — Financial — https://policylayer.com/tools/ai-rokha-rokha/carry-order.md - `creator_earnings` — Financial — https://policylayer.com/tools/ai-rokha-rokha/creator-earnings.md - …and 185 more: https://policylayer.com/tools/ai-rokha-rokha.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=ai-rokha-rokha · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ai-rokha-rokha