check_relay_health
Check the sponsor relay health and nonce status. Use this tool for operator diagnostics around relay-owned sponsor state. It will: - Check relay availability - Inspect sponsor address nonce state - Detect nonce gaps that block transactions - Detect mempool desync (confirmed nonce far behind mempo...
This record as markdown: /tools/io-github-aibtcdev-mcp-server/check-relay-health.md
What check_relay_health does on Aibtc
AI agents call check_relay_health to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_relay_health is rated Low
This is a pure diagnostic/monitoring tool that retrieves and reports status information about relay and transaction state. It performs queries and inspections only, with no data creation, modification, deletion, or execution of transactions. The tool is designed for operator diagnostics and troubleshooting, not for taking actions that would change system state.
From the tool's definition Tool checks relay health status and nonce state without modifying any data. Specific actions listed are: 'Check relay availability', 'Inspect sponsor address nonce state', 'Detect nonce gaps', 'Detect mempool desync', 'List stuck transactions', 'Report…
Attacks that exploit this kind of access
The rule that runs check_relay_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_relay_health, this is the rule to start with:
check_relay_health 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 Aibtc, apply this rule, and every check_relay_health call is checked against it from then on.
Questions about check_relay_health
Check the sponsor relay health and nonce status. Use this tool for operator diagnostics around relay-owned sponsor state. It will: - Check relay availability - Inspect sponsor address nonce state - Detect nonce gaps that block transactions - Detect mempool desync (confirmed nonce far behind mempool nonce) - List stuck transactions with txid, nonce, and how long they have been pending - Report mempool congestion This tool does not redefine caller-facing x402 payment states. Use paymentId polling for payment lifecycle truth; use this output only as backup diagnostics. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for check_relay_health: 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 Aibtc. Nothing to install.
check_relay_health 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_relay_health 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_relay_health. 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_relay_health is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
This server
Across the catalogue