lido_vault_rebalance · Lido MCP Server MCP: Risk & Policy

WHAT IT DOES

What lido_vault_rebalance does on Lido MCP Server

AI agents invoke lido_vault_rebalance 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_vault_rebalance needs a policy

This tool triggers complex financial operations on a staking vault — withdrawing ETH and burning shares — which constitutes execution of an external blockchain operation with significant side effects. Burning shares is irreversible, pushing this toward Destructive, but the primary framing is a rebalancing workflow (a managed operation) rather than a pure deletion.

From the tool's definition Rebalance a staking vault by withdrawing ETH and burning liability shares

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_vault_rebalance Rate-limited

lido_vault_rebalance 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_vault_rebalance": {
      "limits": [
        {
          "counter": "lido_vault_rebalance_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_vault_rebalance

What does the lido_vault_rebalance tool do? +

Rebalance a staking vault by withdrawing ETH and burning liability shares. 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_vault_rebalance? +

Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_vault_rebalance: 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_vault_rebalance? +

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

Can I rate-limit lido_vault_rebalance? +

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

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

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