check_tx_status

SERVERXRPName SOURCE@xrpname/xrpname-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/io-github-xrpdomains-xrpname-mcp-server/check-tx-status.md

WHAT IT DOES

What check_tx_status does on XRPName

AI agents call check_tx_status to retrieve information from XRPName 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
`tx_hash`	string	Yes	64-character hex XRPL transaction hash

Parameters from the server's own tool schema.

RISK

Why check_tx_status is rated Low

Retrieves transaction status without modifying data or executing side effects.

From the tool's definition Check validation status of XRPL transaction by hash. Returns status and engine result code.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_tx_status safely

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

check_tx_status Allowed

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

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

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

FAQ

Questions about check_tx_status

What does the check_tx_status tool do? +

Check the validation status of an XRPL transaction by hash. Use after send_signed_tx to confirm whether the transaction was validated on-ledger. Returns status (pending, validated, failed, not_found) and engine result code. It is categorised as a Read tool in the XRPName MCP Server, which means it retrieves data without modifying state.

What parameters does check_tx_status accept? +

check_tx_status accepts 1 parameter: tx_hash. Required: tx_hash. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on check_tx_status? +

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

What risk level is check_tx_status? +

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

Can I rate-limit check_tx_status? +

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

How do I block check_tx_status completely? +

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

What MCP server provides check_tx_status? +

check_tx_status is provided by the XRPName MCP server (@xrpname/xrpname-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on XRPName, and thousands of servers like it.

This server

All 10 XRPName tools →

Across the catalogue

claude_git_status on Claude Bridge → The MCP Attack Database →

Guides

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