Check if a chain is healthy, view available solver liquidity, solver wallet addresses, depository contracts, and optionally check route configuration between two chains. Use this before quoting to verify a route is viable: - Is the chain healthy and operational? - How much solver liquidity is ava...
AI agents call check_chain_status to retrieve information from Relay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only operations to query blockchain network status, liquidity levels, and contract addresses. It has no side effects, does not execute transactions, does not move funds, and does not modify any state. It is a prerequisite check before other operations and returns informational data to help agents make decisions about bridge routes.
From the tool's definition Tool description states: 'Check if a chain is healthy, view available solver liquidity, solver wallet addresses, depository contracts' - purely informational queries with no state modification.
Attacks that exploit this kind of access
Check if a chain is healthy, view available solver liquidity, solver wallet addresses, depository contracts, and optionally check route configuration between two chains. Use this before quoting to verify a route is viable: - Is the chain healthy and operational? - How much solver liquidity is available? - What are the solver EOA addresses and Relay contracts on this chain? - Is the route between origin and destination enabled? If a chain is unhealthy or has low liquidity, bridging may fail or be slow. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server MCP server in PolicyLayer and add a rule for check_chain_status: 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 Relay MCP Server. Nothing to install.
check_chain_status 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 check_chain_status 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 check_chain_status. 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.
check_chain_status is provided by the Relay MCP Server MCP server (relayprotocol/relay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →