get_debridge_order_ids_by_tx_hash
Retrieves all deBridge order IDs created in a single transaction.
This record as markdown: /tools/testinguser1111111-sei-mcp-server/get-debridge-order-ids-by-tx-hash.md
What get_debridge_order_ids_by_tx_hash does on SEI MCP Server V2
AI agents call get_debridge_order_ids_by_tx_hash to retrieve information from SEI MCP Server V2 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_debridge_order_ids_by_tx_hash is rated Low
This tool performs a simple data lookup operation — it queries existing deBridge order IDs indexed by a transaction hash. There is no creation, modification, deletion, or execution of transactions. No funds are moved, no blockchain state is altered, and no code is executed. It is purely informational retrieval from on-chain data, making it a Read category risk with low severity.
From the tool's definition Tool retrieves/queries deBridge order IDs by transaction hash. Verb 'Retrieves' and action 'get' indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs get_debridge_order_ids_by_tx_hash safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_debridge_order_ids_by_tx_hash, this is the rule to start with:
get_debridge_order_ids_by_tx_hash 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 SEI MCP Server V2, apply this rule, and every get_debridge_order_ids_by_tx_hash call is checked against it from then on.
Questions about get_debridge_order_ids_by_tx_hash
Retrieves all deBridge order IDs created in a single transaction. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for get_debridge_order_ids_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.
get_debridge_order_ids_by_tx_hash 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_debridge_order_ids_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.
Set action: deny in the PolicyLayer policy for get_debridge_order_ids_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.
get_debridge_order_ids_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.
More on SEI MCP Server V2, and thousands of servers like it.
This server
Across the catalogue