Claim USDB residue from a liquidated leverage position. Position must be inactive (already liquidated) and have a non-zero claim. Uses loanId (leverage position id), NOT hubId.
AI agents use claim_leverage_liquidation to commit financial operations through Basis MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool claims financial assets (USDB tokens) from a liquidated leverage position on a DeFi protocol. It involves moving cryptocurrency/tokens to the caller, constituting a financial operation. Misuse could result in unauthorized claiming of funds or irreversible financial transactions on-chain.
From the tool's definition Claim USDB residue from a liquidated leverage position... loanId (leverage position id)
Attacks that exploit this kind of access
Claim USDB residue from a liquidated leverage position. Position must be inactive (already liquidated) and have a non-zero claim. Uses loanId (leverage position id), NOT hubId. 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 claim_leverage_liquidation: 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.
claim_leverage_liquidation 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 claim_leverage_liquidation 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 claim_leverage_liquidation. 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.
claim_leverage_liquidation 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 →