AI agents call get_leveraged_token_order_record to retrieve information from Bybit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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.
Attacks that exploit this kind of access
Get leveraged token purchase/redemption records. It is categorised as a Read tool in the Bybit MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP server in PolicyLayer and add a rule for get_leveraged_token_order_record: 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 Bybit. Nothing to install.
get_leveraged_token_order_record 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_leveraged_token_order_record 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_leveraged_token_order_record. 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_leveraged_token_order_record is provided by the Bybit MCP server (johnnywic/bybit-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 →