AI agents use crypto_loan_borrow to commit financial operations through Bybit — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly executes a crypto loan borrowing operation, which creates a real financial obligation (debt) on the exchange. Misuse could result in significant financial liability, margin calls, or liquidation. Financial category applies as it commits financial obligations, and severity is critical due to the irreversible nature of borrowing and potential for large monetary exposure.
From the tool's definition 'Borrow via crypto loan' - initiates a financial borrowing transaction on Bybit exchange, committing financial obligations
Attacks that exploit this kind of access
Borrow via crypto loan. 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 crypto_loan_borrow: 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.
crypto_loan_borrow 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 crypto_loan_borrow 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 crypto_loan_borrow. 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.
crypto_loan_borrow 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 →