Transfer rebasing stETH to another address on Optimism.
AI agents use lido_l2_transfer_steth to create or update resources in Lido MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lido MCP Server environment.
This tool transfers stETH tokens to another address on Optimism L2. It modifies blockchain state by moving assets between addresses. While reversible in principle (the recipient could send back), token transfers are practically irreversible and involve real financial assets.
From the tool's definition Transfer rebasing stETH to another address on Optimism
Attacks that exploit this kind of access
Transfer rebasing stETH to another address on Optimism. It is categorised as a Write tool in the Lido MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_l2_transfer_steth: 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_l2_transfer_steth is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the lido_l2_transfer_steth 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_l2_transfer_steth. 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_l2_transfer_steth 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 →