Deep diagnostic view correlating sender nonces with sponsor nonces for sponsored transactions. Reads the sender's local pending txid log and cross-references each entry against the sponsor's mempool to show the full lifecycle of sponsored transactions: - Which sender nonce maps to which sponsor ...
Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call tx_status_deep to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though tx_status_deep only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
tx_status_deep:
rules:
- action: allowSee the full Aibtc policy for all 288 tools.
Deep diagnostic view correlating sender nonces with sponsor nonces for sponsored transactions. Reads the sender's local pending txid log and cross-references each entry against the sponsor's mempool to show the full lifecycle of sponsored transactions: - Which sender nonce maps to which sponsor nonce - Whether sponsor nonce gaps are blocking specific transactions - Which pending txids are missing from the sponsor mempool entirely - Multiple competing txids (RBF candidates) for the same sender nonce slot Output per nonce slot: Sender nonce N: - 0xabc (sponsored, sponsor nonce 47) -- BLOCKED by missing sponsor nonces [44, 45] - 0xdef (direct, fee 0.01 STX) -- competing RBF candidate Sender nonce M (0xghi, sponsored) -> sponsor nonce 48 -- pending, no gaps ahead Sender nonce P (0xjkl, sponsored) -> NOT IN SPONSOR MEMPOOL Use this when check_relay_health shows issues but you need per-transaction clarity. Returns structured JSON with pendingSlots, sponsorMissingNonces, and summary counts.. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for tx_status_deep. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.
tx_status_deep 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 tx_status_deep rule in your Intercept 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 Intercept policy for tx_status_deep. 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.
tx_status_deep is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept