close_leverage
Close (or partially close) a leverage position. 10% increments.
This record as markdown: /tools/launch-on-basis-mcp-ts/close-leverage.md
What close_leverage does on Basis MCP Server
AI agents use close_leverage to commit financial operations through Basis MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why close_leverage is rated Critical
Closing a leverage position is a financial operation that settles outstanding margin/leveraged trades, potentially realizing gains or losses and moving funds. On a DeFi protocol like Basis on BNB Smart Chain, misuse could result in premature position closure, significant financial loss, or liquidation-level consequences. This clearly falls under Financial, which is the most severe applicable category.
From the tool's definition 'Close (or partially close) a leverage position' — directly closes financial leverage positions, which are financial instruments involving borrowed capital on a trading protocol
Attacks that exploit this kind of access
The rule that runs close_leverage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For close_leverage, this is the rule to start with:
Any call to close_leverage is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every close_leverage call is checked against it from then on.
Questions about close_leverage
Close (or partially close) a leverage position. 10% increments. 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 close_leverage: 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.
close_leverage 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 close_leverage 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 close_leverage. 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.
close_leverage 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.
More on Basis MCP Server, and thousands of servers like it.
Across the catalogue