prepare_lido_unwrap
Build an unsigned wstETH.unwrap transaction that converts wstETH (non-rebasing) back into stETH (rebasing). No approval needed — burns wstETH from the caller's balance.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-lido-unwrap.md
What prepare_lido_unwrap does on VaultPilot MCP
AI agents invoke prepare_lido_unwrap to trigger actions in VaultPilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet | string | Yes | |
amountWstETH | string | Yes | Human-readable wstETH amount to unwrap into stETH, NOT raw wei. Example: "0.5" for 0.5 wstETH (18 decimals). |
Parameters from the server's own tool schema.
Why prepare_lido_unwrap is rated High
This is Execute rather than Destructive because the transaction is unsigned and reversible in principle (the caller can choose not to sign and broadcast it, and the underlying operation itself—unwrapping wstETH into stETH—is a normal DeFi operation, not a data deletion).
From the tool's definition Tool description states it 'Build[s] an unsigned wstETH.unwrap transaction' that 'burns wstETH from the caller's balance.' The action directly modifies token balances through a contract call, converting one asset form to another with irreversible effects on…
Attacks that exploit this kind of access
The rule that runs prepare_lido_unwrap safely
PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prepare_lido_unwrap, this is the rule to start with:
prepare_lido_unwrap stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_lido_unwrap call is checked against it from then on.
Questions about prepare_lido_unwrap
Build an unsigned wstETH.unwrap transaction that converts wstETH (non-rebasing) back into stETH (rebasing). No approval needed — burns wstETH from the caller's balance. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
prepare_lido_unwrap accepts 2 parameters: wallet, amountWstETH. Required: wallet, amountWstETH. The full parameter table on this page comes from the server's own tool schema.
Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_lido_unwrap: 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 VaultPilot MCP. Nothing to install.
prepare_lido_unwrap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prepare_lido_unwrap 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 prepare_lido_unwrap. 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.
prepare_lido_unwrap is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on VaultPilot, and thousands of servers like it.
Across the catalogue