lido_wrap_eth_to_wsteth · Lido MCP Server MCP: Risk & Policy

WHAT IT DOES

What lido_wrap_eth_to_wsteth does on Lido MCP Server

AI agents invoke lido_wrap_eth_to_wsteth to trigger actions in Lido MCP Server. 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.

WHY IT NEEDS A POLICY

Why lido_wrap_eth_to_wsteth needs a policy

This tool executes an on-chain transaction that stakes ETH into the Lido protocol and wraps it to wstETH. While it involves moving assets (ETH), it is not a direct financial transfer like a payment or trade — it is a protocol interaction that executes a complex multi-step blockchain operation.

From the tool's definition Stake ETH and wrap to wstETH in a single transaction

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_wrap_eth_to_wsteth Rate-limited

lido_wrap_eth_to_wsteth 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lido_wrap_eth_to_wsteth": {
      "limits": [
        {
          "counter": "lido_wrap_eth_to_wsteth_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lido MCP Server, so you can run agents against it safely.

FAQ

Questions about lido_wrap_eth_to_wsteth

What does the lido_wrap_eth_to_wsteth tool do? +

Stake ETH and wrap to wstETH in a single transaction. It is categorised as a Execute tool in the Lido MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lido_wrap_eth_to_wsteth? +

Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_wrap_eth_to_wsteth: 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.

What risk level is lido_wrap_eth_to_wsteth? +

lido_wrap_eth_to_wsteth is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lido_wrap_eth_to_wsteth? +

Yes. Add a rate_limit block to the lido_wrap_eth_to_wsteth 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.

How do I block lido_wrap_eth_to_wsteth completely? +

Set action: deny in the PolicyLayer policy for lido_wrap_eth_to_wsteth. 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.

What MCP server provides lido_wrap_eth_to_wsteth? +

lido_wrap_eth_to_wsteth 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.