tx_status_deep

Deep diagnostic view correlating sender nonces with sponsor nonces for sponsored transactions. Reads the sender

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/tx-status-deep.md

WHAT IT DOES

What tx_status_deep does on Aibtc

AI agents call tx_status_deep 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 tx_status_deep is rated Low

This tool retrieves and displays diagnostic information about transaction states and nonce correlations. It has no capability to modify data, execute operations, or trigger state changes. The 'deep diagnostic view' language and explicit 'Reads the sender' confirm it is a read-only inspection tool with minimal security risk.

From the tool's definition Tool description states 'Deep diagnostic view' and 'Reads the sender' — purely informational retrieval with no modification or side effects. The function correlates nonces for diagnostics, which is a query/inspection activity.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tx_status_deep Allowed

tx_status_deep 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": {
    "tx_status_deep": {}
  }
}

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 tx_status_deep call is checked against it from then on.

FAQ

Questions about tx_status_deep

What does the tx_status_deep tool do? +

Deep diagnostic view correlating sender nonces with sponsor nonces for sponsored transactions. Reads the sender. 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 tx_status_deep? +

Register the Aibtc MCP server in PolicyLayer and add a rule for tx_status_deep: 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 tx_status_deep? +

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

Can I rate-limit tx_status_deep? +

Yes. Add a rate_limit block to the tx_status_deep 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 tx_status_deep completely? +

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

What MCP server provides tx_status_deep? +

tx_status_deep 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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