get_leveraged_token_order_record

What get_leveraged_token_order_record does on Bybit

AI agents call get_leveraged_token_order_record to retrieve information from Bybit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_leveraged_token_order_record is rated Low

This tool retrieves historical order records for leveraged tokens. It queries existing data without side effects, making it a Read operation. While the Bybit server includes many Financial and Destructive tools (payment processing, order cancellation, margin modification), this specific tool only accesses past transaction history.

From the tool's definition Tool name 'get_leveraged_token_order_record' uses the 'get' verb and description states 'Get leveraged token purchase/redemption records' — purely a retrieval operation with no modification, deletion, or financial transaction capability.

The rule that runs get_leveraged_token_order_record safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_leveraged_token_order_record": {}
  }
}

Questions about get_leveraged_token_order_record