AI agents use purchase_leveraged_token to commit financial operations through Bybit — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Purchasing a leveraged token involves spending funds to acquire a financial instrument. This is a direct financial transaction with real monetary consequences, placing it in the Financial category. The severity is critical because an AI agent misusing this tool could make unauthorized purchases of leveraged tokens, resulting in significant financial losses.
From the tool's definition Purchase a leveraged token" — explicitly commits a financial transaction by buying a leveraged token on the Bybit exchange.
Attacks that exploit this kind of access
Purchase a leveraged token. It is categorised as a Financial tool in the Bybit MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bybit MCP server in PolicyLayer and add a rule for purchase_leveraged_token: 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.
purchase_leveraged_token is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the purchase_leveraged_token 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 purchase_leveraged_token. 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.
purchase_leveraged_token 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 →