get_transaction_status

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 42 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/get-transaction-status.md

WHAT IT DOES

What get_transaction_status does on VaultPilot MCP

AI agents call get_transaction_status to retrieve information from VaultPilot MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`chain`	string	Yes	EVM chain, 'tron', 'solana', or 'bitcoin'.
`txHash`	string	Yes	Transaction identifier. EVM: 32-byte hex (0x-prefixed or bare). TRON: 32-byte bare hex. Solana: 64-byte signature as base58 (86–88 chars). Bitcoin: 32-byte bare
`durableNonce`	object	—	Solana only, durable-nonce txs (native_send, spl_send, nonce_close, jupiter_swap, all marginfi_* actions). Returned by send_transaction on these flows. When sup
`lastValidBlockHeight`	integer	—	Solana only, legacy-blockhash txs (currently just `nonce_init`). Block-height ceiling for the tx's baked blockhash — returned by send_transaction for such txs.

Parameters from the server's own tool schema.

RISK

Why get_transaction_status is rated Low

This tool only queries and retrieves transaction status information from blockchain nodes. It performs no writes, deletions, code execution, or financial operations. The polling of transaction state and status checking is a read-only operation with no side effects.

From the tool's definition Tool description states 'Poll a transaction's status' and 'Returns pending / success / failed'. The tool reads transaction status from blockchain RPC endpoints (EVM, Solana, TronGrid) and nonce accounts without modifying any state.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_transaction_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_transaction_status, this is the rule to start with:

get_transaction_status Allowed

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

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

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

FAQ

Questions about get_transaction_status

What does the get_transaction_status tool do? +

Poll a transaction's status via the chain's RPC (EVM / Solana) or TronGrid (TRON). Returns pending / success / failed, plus 'dropped' on Solana when the tx is mathematically unable to land. Pass chain='tron' with the bare hex txID for TRON; chain='solana' with the base58 signature for Solana. For Solana, ALSO pass whichever drop-detection field send_transaction returned: (a) durableNonce for nearly every send (native/SPL sends, nonce_close, jupiter_swap, all marginfi_* actions) — the tool reads the on-chain nonce account and reports 'dropped' if it rotated past the baked value; or (b) lastValidBlockHeight for legacy-blockhash txs (currently just nonce_init) — reports 'dropped' if current block height is past. Without either field the tool reports 'pending' forever for dropped txs. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_transaction_status accept? +

get_transaction_status accepts 4 parameters: chain, txHash, durableNonce, lastValidBlockHeight. Required: chain, txHash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_transaction_status? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for get_transaction_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 VaultPilot MCP. Nothing to install.

What risk level is get_transaction_status? +

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

Can I rate-limit get_transaction_status? +

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

How do I block get_transaction_status completely? +

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

What MCP server provides get_transaction_status? +

get_transaction_status is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

get_task_status on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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