prepare_lido_unwrap · VaultPilot MCP: Risk & Policy

WHAT IT DOES

What prepare_lido_unwrap does on VaultPilot MCP

AI agents invoke prepare_lido_unwrap to trigger actions in VaultPilot MCP. 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.

PARAMETERS

Parameter	Type	Required	Description
`wallet`	string	Yes
`amountWstETH`	string	Yes	Human-readable wstETH amount to unwrap into stETH, NOT raw wei. Example: "0.5" for 0.5 wstETH (18 decimals).

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why prepare_lido_unwrap needs a policy

prepare_lido_unwrap triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

prepare_lido_unwrap Rate-limited

prepare_lido_unwrap 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": {
    "prepare_lido_unwrap": {
      "limits": [
        {
          "counter": "prepare_lido_unwrap_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 VaultPilot MCP, so you can run agents against it safely.

FAQ

Questions about prepare_lido_unwrap

What does the prepare_lido_unwrap tool do? +

Build an unsigned wstETH.unwrap transaction that converts wstETH (non-rebasing) back into stETH (rebasing). No approval needed — burns wstETH from the caller's balance. It is categorised as a Execute tool in the VaultPilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does prepare_lido_unwrap accept? +

prepare_lido_unwrap accepts 2 parameters: wallet, amountWstETH. Required: wallet, amountWstETH. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on prepare_lido_unwrap? +

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

What risk level is prepare_lido_unwrap? +

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

Can I rate-limit prepare_lido_unwrap? +

Yes. Add a rate_limit block to the prepare_lido_unwrap 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 prepare_lido_unwrap completely? +

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

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