prepare_lido_stake
Build an unsigned Lido stake transaction (wraps ETH into stETH via stETH.submit). The tx's value field is the ETH amount to stake.
This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/prepare-lido-stake.md
What prepare_lido_stake does on VaultPilot MCP
AI agents use prepare_lido_stake to commit financial operations through VaultPilot MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
wallet | string | Yes | |
amountEth | string | Yes | Human-readable ETH amount, NOT raw wei. Example: "0.5" for 0.5 ETH. |
Parameters from the server's own tool schema.
Why prepare_lido_stake is rated Critical
This tool constructs a transaction that commits real ETH into the Lido staking protocol, converting it to stETH. While it builds an 'unsigned' transaction, it directly prepares a financial operation that moves crypto assets (ETH) into a staking contract, committing financial obligations. On a self-custodial crypto MCP with Ledger signing, this is the direct precursor to an irreversible financial commitment.
From the tool's definition 'Build an unsigned Lido stake transaction (wraps ETH into stETH via stETH.submit). The tx's value field is the ETH amount to stake.'
Attacks that exploit this kind of access
The rule that runs prepare_lido_stake 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_stake, this is the rule to start with:
Any call to prepare_lido_stake is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every prepare_lido_stake call is checked against it from then on.
Questions about prepare_lido_stake
Build an unsigned Lido stake transaction (wraps ETH into stETH via stETH.submit). The tx's value field is the ETH amount to stake. It is categorised as a Financial tool in the VaultPilot MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
prepare_lido_stake accepts 2 parameters: wallet, amountEth. Required: wallet, amountEth. 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_stake: 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_stake 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 prepare_lido_stake 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_stake. 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_stake 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