lido_approve_withdrawal_nft · Lido MCP Server MCP

WHAT IT DOES

What lido_approve_withdrawal_nft does on Lido MCP Server

AI agents use lido_approve_withdrawal_nft to create or update resources in Lido MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lido MCP Server environment.

WHY IT NEEDS A POLICY

Why lido_approve_withdrawal_nft needs a policy

This falls under Write category because it creates a reversible modification to on-chain state—specifically, granting approval/authorization for NFT transfers. It is not Destructive since the approval can be revoked, nor Destructive since it does not delete or irreversibly consume data.

From the tool's definition The tool explicitly performs an approval action (lido_approve_withdrawal_nft) that modifies token authorization state on-chain by granting transfer rights to a withdrawal request NFT.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lido_approve_withdrawal_nft Rate-limited

lido_approve_withdrawal_nft stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_approve_withdrawal_nft": {
      "limits": [
        {
          "counter": "lido_approve_withdrawal_nft_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_approve_withdrawal_nft

What does the lido_approve_withdrawal_nft tool do? +

Approve an address to transfer a specific withdrawal request NFT. It is categorised as a Write tool in the Lido MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lido_approve_withdrawal_nft? +

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

lido_approve_withdrawal_nft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lido_approve_withdrawal_nft? +

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

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

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