nonce_health

Check the sender nonce health for the active wallet. Compares the local nonce tracker state (persisted at ~/.aibtc/nonce-state.json) against the chain

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/nonce-health.md

WHAT IT DOES

What nonce_health does on Aibtc

AI agents call nonce_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.

RISK

Why nonce_health is rated Low

This tool retrieves and compares nonce state information for diagnostic/informational purposes. It has no side effects, does not modify data, does not execute transactions, and does not delete or create resources. The blast radius of misuse is minimal — an attacker can at most learn about wallet nonce state, which is not sensitive enough to escalate beyond low severity.

From the tool's definition Tool description states 'Check the sender nonce health' and 'Compares the local nonce tracker state against the chain' — these are read-only query operations with no data modification or external execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nonce_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 nonce_health, this is the rule to start with:

nonce_health Allowed

nonce_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nonce_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every nonce_health call is checked against it from then on.

FAQ

Questions about nonce_health

What does the nonce_health tool do? +

Check the sender nonce health for the active wallet. Compares the local nonce tracker state (persisted at ~/.aibtc/nonce-state.json) against the chain. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nonce_health? +

Register the Aibtc MCP server in PolicyLayer and add a rule for nonce_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.

What risk level is nonce_health? +

nonce_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nonce_health? +

Yes. Add a rate_limit block to the nonce_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.

How do I block nonce_health completely? +

Set action: deny in the PolicyLayer policy for nonce_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.

What MCP server provides nonce_health? +

nonce_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.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →