Open leveraged position. NO price liquidation — time-based only. Simulates first, requires confirm=true.
AI agents use leverage_buy to commit financial operations through Basis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Opening a leveraged position directly commits financial capital with amplified risk. It is a financial operation (borrowing funds to trade) on a live blockchain protocol, making it Financial category with critical severity due to leverage amplification of potential losses and irreversible on-chain commitment once confirmed.
From the tool's definition 'Open leveraged position' — uses leverage to commit financial obligations; 'leverage_buy' in context of trading protocol on BNB Smart Chain involving loans and trading
Attacks that exploit this kind of access
Open leveraged position. NO price liquidation — time-based only. Simulates first, requires confirm=true. It is categorised as a Financial tool in the Basis MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for leverage_buy: 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 Basis MCP Server. Nothing to install.
leverage_buy 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 leverage_buy 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 leverage_buy. 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.
leverage_buy is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). 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 →