Check the status of a Relay bridge or swap transaction. Returns rich data including fees, token amounts, fail reasons, and route details. Accepts either a requestId (from a previous quote/execution) or a txHash (on-chain transaction hash) to look up the request. Note: Quotes expire in ~30 seconds...
AI agents call get_transaction_status to retrieve information from Relay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries transaction state information without modifying data, executing code, or affecting financial systems. It is a read-only lookup operation with no side effects. The low severity reflects minimal risk from misuse, as reading transaction status cannot cause harm even if an agent queries arbitrary transaction IDs.
From the tool's definition Tool description states it 'Check[s] the status of a Relay bridge or swap transaction' and 'Returns rich data including fees, token amounts, fail reasons, and route details.' It accepts a requestId or txHash as input parameters to 'look up the request.' No…
Attacks that exploit this kind of access
Check the status of a Relay bridge or swap transaction. Returns rich data including fees, token amounts, fail reasons, and route details. Accepts either a requestId (from a previous quote/execution) or a txHash (on-chain transaction hash) to look up the request. Note: Quotes expire in ~30 seconds. If tracking a completed transaction, use the requestId from the execution response or the on-chain txHash — not the quote ID. If get_transaction_status returns. It is categorised as a Read tool in the Relay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Relay MCP Server 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 Relay MCP Server. Nothing to install.
get_transaction_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 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.
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.
get_transaction_status is provided by the Relay MCP Server MCP server (relayprotocol/relay-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →