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...
This record as markdown: /tools/ai-rokha-rokha/singularityagent--chain-liveness.md
What singularityagent__chain_liveness does on Rokha
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
chain | array | — | Chain ids or aliases to check. Defaults to every configured chain. |
Parameters from the server's own tool schema.
Why singularityagent__chain_liveness is rated Low
Tool queries blockchain liveness status without modifying data or triggering external operations.
From the tool's definition Check that a chain is actually producing blocks, probes endpoints separately
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs singularityagent__chain_liveness safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For singularityagent__chain_liveness, this is the rule to start with:
singularityagent__chain_liveness is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every singularityagent__chain_liveness call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
singularityagent__chain_liveness accepts 1 parameter: chain. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for singularityagent__chain_liveness: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rokha. Nothing to install.
singularityagent__chain_liveness is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the singularityagent__chain_liveness rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for singularityagent__chain_liveness. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
singularityagent__chain_liveness is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue