prepare_lido_stake · VaultPilot MCP: Risk & Policy

WHAT IT DOES

What prepare_lido_stake does on VaultPilot MCP

AI agents invoke prepare_lido_stake 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
`amountEth`	string	Yes	Human-readable ETH amount, NOT raw wei. Example: "0.5" for 0.5 ETH.

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why prepare_lido_stake needs a policy

prepare_lido_stake 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_stake Rate-limited

prepare_lido_stake 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_stake": {
      "limits": [
        {
          "counter": "prepare_lido_stake_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_stake

What does the prepare_lido_stake tool do? +

Build an unsigned Lido stake transaction (wraps ETH into stETH via stETH.submit). The tx's value field is the ETH amount to stake. 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_stake accept? +

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

How do I enforce a policy on prepare_lido_stake? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for prepare_lido_stake: 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_stake? +

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

Can I rate-limit prepare_lido_stake? +

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

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

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