Stake ETH with Lido to receive stETH.
AI agents use lido_stake_eth to commit financial operations through Lido MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves ETH (a financial asset) into the Lido protocol in exchange for stETH tokens. This constitutes a financial commitment — transferring ETH out of the user's wallet and locking it in a staking contract. Misuse could result in unintended ETH being staked, potentially with slippage, lock-up considerations, or loss of funds if misused at scale, making it a high-severity financial operation.
From the tool's definition Stake ETH with Lido to receive stETH
Attacks that exploit this kind of access
Stake ETH with Lido to receive stETH. It is categorised as a Financial tool in the Lido MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_stake_eth: 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 Lido MCP Server. Nothing to install.
lido_stake_eth 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 lido_stake_eth 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 lido_stake_eth. 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.
lido_stake_eth is provided by the Lido MCP Server MCP server (the-wunmi/lido-mcp-server). 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 →