withdraw_yei_asset
Withdraw a supplied asset from the Yei Finance pool.
This record as markdown: /tools/testinguser1111111-sei-mcp-server/withdraw-yei-asset.md
What withdraw_yei_asset does on SEI MCP Server V2
AI agents use withdraw_yei_asset to commit financial operations through SEI MCP Server V2, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why withdraw_yei_asset is rated Critical
Withdrawing a supplied asset from a DeFi lending pool (Yei Finance) is a financial operation that moves cryptocurrency assets. Misuse could drain supplied collateral, potentially triggering liquidations or loss of funds, making this a high-severity financial action.
From the tool's definition 'Withdraw a supplied asset from the Yei Finance pool' — moves deposited/supplied assets out of a DeFi lending protocol
Attacks that exploit this kind of access
The rule that runs withdraw_yei_asset safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For withdraw_yei_asset, this is the rule to start with:
Any call to withdraw_yei_asset is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every withdraw_yei_asset call is checked against it from then on.
Questions about withdraw_yei_asset
Withdraw a supplied asset from the Yei Finance pool. It is categorised as a Financial tool in the SEI MCP Server V2 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the SEI MCP Server V2 MCP server in PolicyLayer and add a rule for withdraw_yei_asset: 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 SEI MCP Server V2. Nothing to install.
withdraw_yei_asset 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 withdraw_yei_asset 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 withdraw_yei_asset. 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.
withdraw_yei_asset is provided by the SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SEI MCP Server V2, and thousands of servers like it.
Across the catalogue