Withdraw supplied assets and accrued interest from HyperLend protocol lending pools back to your wallet
AI agents use hyperevmWithdraw to commit financial operations through HyperEVM MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves crypto assets (supplied tokens plus accrued interest) from a lending protocol back to the user's wallet, constituting a financial transaction on a DeFi protocol. Misuse could result in unintended withdrawals of funds from lending positions, affecting financial obligations and portfolio state. Financial > Destructive applies here as it moves monetary value.
From the tool's definition Withdraw supplied assets and accrued interest from HyperLend protocol lending pools back to your wallet
Attacks that exploit this kind of access
Withdraw supplied assets and accrued interest from HyperLend protocol lending pools back to your wallet. It is categorised as a Financial tool in the HyperEVM MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the HyperEVM MCP server in PolicyLayer and add a rule for hyperevmWithdraw: 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 HyperEVM MCP. Nothing to install.
hyperevmWithdraw 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 hyperevmWithdraw 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 hyperevmWithdraw. 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.
hyperevmWithdraw is provided by the HyperEVM MCP server (playainetwork/hyperevm-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 →