get_debridge_order_by_tx_hash

Retrieves the details of a deBridge order by its creation transaction hash.

Server SEI MCP Server V2 testinguser1111111/sei-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_debridge_order_by_tx_hash does on SEI MCP Server V2

AI agents call get_debridge_order_by_tx_hash to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_debridge_order_by_tx_hash needs a policy

This tool queries blockchain data to fetch order details by transaction hash. It performs read-only data retrieval without creating, modifying, deleting, or executing any operations. The blast radius if misused by an AI agent is minimal—worst case is information disclosure about orders the agent can already see on-chain.

From the tool's definition Tool name contains 'get_' and description states 'Retrieves the details of a deBridge order' — a pure data retrieval operation with no side effects, modifications, or execution.

Questions about get_debridge_order_by_tx_hash

What does the get_debridge_order_by_tx_hash tool do? +

Retrieves the details of a deBridge order by its creation transaction hash. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_debridge_order_by_tx_hash? +

Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for get_debridge_order_by_tx_hash: 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 SEI MCP Server V2. Nothing to install.

What risk level is get_debridge_order_by_tx_hash? +

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

Can I rate-limit get_debridge_order_by_tx_hash? +

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

Set action: deny in the PolicyLayer policy for get_debridge_order_by_tx_hash. 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_debridge_order_by_tx_hash? +

get_debridge_order_by_tx_hash is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.