sol_tx_status
Fast confirmation check for up to 100 Solana transaction signatures in one call (getSignatureStatuses with history search): found or not, processed / confirmed / finalized, success or the on-chain error, slot and confirmations, plus counts. Built for agents polling payments or swaps they just sen...
This record as markdown: /tools/com-it-scorptech-x402/sol-tx-status.md
What sol_tx_status does on ScorpTech x402 API
AI agents call sol_tx_status to retrieve information from ScorpTech x402 API 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 |
|---|---|---|---|
signatures | array | Yes | Transaction signatures (base58), comma list or JSON array, max 100 |
searchHistory | boolean | — | Also search older ledger history (not only the recent status cache) |
Parameters from the server's own tool schema.
Why sol_tx_status is rated Low
Even though sol_tx_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sol_tx_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sol_tx_status, this is the rule to start with:
sol_tx_status 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 ScorpTech x402 API, apply this rule, and every sol_tx_status call is checked against it from then on.
Questions about sol_tx_status
Fast confirmation check for up to 100 Solana transaction signatures in one call (getSignatureStatuses with history search): found or not, processed / confirmed / finalized, success or the on-chain error, slot and confirmations, plus counts. Built for agents polling payments or swaps they just sent. Public Solana RPC, read-only. Price: $0.002 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/sol-tx-status. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
sol_tx_status accepts 2 parameters: signatures, searchHistory. Required: signatures. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for sol_tx_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 ScorpTech x402 API. Nothing to install.
sol_tx_status 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 sol_tx_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.
Set action: deny in the PolicyLayer policy for sol_tx_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.
sol_tx_status is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue