lido_request_withdrawal · Lido MCP Server MCP: Risk & Policy

WHAT IT DOES

What lido_request_withdrawal does on Lido MCP Server

AI agents invoke lido_request_withdrawal 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_request_withdrawal needs a policy

This tool initiates a withdrawal transaction on the Lido protocol, which triggers an external on-chain operation that moves assets from a staking position and creates a withdrawal NFT. It is not purely destructive (the NFT represents the claim and can be used later), but it executes a significant external blockchain operation with real financial asset implications.

From the tool's definition Request a withdrawal of stETH or wstETH from Lido. Creates a withdrawal NFT.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_request_withdrawal Rate-limited

lido_request_withdrawal 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_request_withdrawal": {
      "limits": [
        {
          "counter": "lido_request_withdrawal_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_request_withdrawal

What does the lido_request_withdrawal tool do? +

Request a withdrawal of stETH or wstETH from Lido. Creates a withdrawal NFT. 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_request_withdrawal? +

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

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

Can I rate-limit lido_request_withdrawal? +

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

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

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