Transfer stETH, wstETH, or LDO tokens to another address.
AI agents use lido_transfer_token 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 directly moves cryptocurrency assets between addresses, which is a financial operation. The blast radius is critical because an AI agent misusing this tool could transfer entire token balances to attacker-controlled addresses, resulting in permanent loss of funds or governance power.
From the tool's definition Tool enables transfer of stETH, wstETH, and LDO tokens to another address—all of which represent financial value (staking derivatives and governance tokens).
Attacks that exploit this kind of access
Transfer stETH, wstETH, or LDO tokens to another address. 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_transfer_token: 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_transfer_token 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_transfer_token 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_transfer_token. 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_transfer_token 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 →