lido_vault_withdraw · Lido MCP Server MCP: Risk & Policy

WHAT IT DOES

What lido_vault_withdraw does on Lido MCP Server

AI agents use lido_vault_withdraw to commit financial operations through Lido MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

WHY IT NEEDS A POLICY

Why lido_vault_withdraw needs a policy

This tool moves ETH out of a Lido staking vault, which constitutes a financial operation involving real cryptocurrency assets. Misuse could result in unauthorized withdrawal of ETH funds, making it a critical financial risk.

From the tool's definition Withdraw ETH from a Lido staking vault via VaultHub

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_vault_withdraw Approval-gated

Any call to lido_vault_withdraw is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lido_vault_withdraw": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE 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_withdraw

What does the lido_vault_withdraw tool do? +

Withdraw ETH from a Lido staking vault via VaultHub. It is categorised as a Financial tool in the Lido MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on lido_vault_withdraw? +

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

lido_vault_withdraw is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit lido_vault_withdraw? +

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

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

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